Skip to content

Context: create standards for the reason for the error after an error exit #33

@markboots

Description

@markboots

From @ggiraldez:
I'm not sure it's written in another part of the document, but for error exits we need a way to indicate the reason for the error. Eg. it may make sense to differentiate between a timeout vs. an invalid option in a multiple choice block.

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