Skip to content

Better error handling #22

@squito

Description

@squito

if something goes wrong during parsing, the error messages are often unclear.

The good news is, at the very least you always get a usage message. But I think lots of error messages get swallowed, some aren't the most meaningful, etc.

Also, its not clear what kind of error a user should throw in their own parsers & validation functions to get nice messages.

maybe this can be resolved just be documenting existing functionality ...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions