Skip to content

Organize different classes of messages more systematically, perhaps follow pylint style #14

@nonprofittechy

Description

@nonprofittechy

This is going to break at some point. It would be nice to start organizing types of errors better (i.e. something like pylint's messages), but if you don't want to do that right now, then putting the specific "not defined on this screen" as a global constant, and then using that constant in all of the error logs where it's used would be a good enough indication that string is required.

Alternatively, start returning more args with err, but that would also have far reaching consequences.

Originally posted by @BryceStevenWilley in #11 (comment)

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