Skip to content

Initial steps on organizing scripts/responses #15

@dmurta1

Description

@dmurta1

Describe what is wrong
There is no example on how scripts should be implemented, their expected complexity, and when a scripts should be broken down in multiple script to avoid a overly complex script

Describe what was expected
A cookbook section showing at least one case (without code) on how scripts should be organized, and how to link scripts to help a user navigate between them

Additional context
If i'm a new user, should I implement a script with multiple optional groupBys, or break one response/script into multiple?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions