Skip to content

[FEATURE] Error code naming scheme #2

Description

@LukeS-05

Caution

Do not share sensitive information. GitHub Issues are public and can be read by any visitor!

Is your feature request related to a problem? Please describe.
The error code scheme is inconsistent and doesn't make sense, given that the prefix 2 was inherited from the old project and has been used for all error codes.

Describe the solution you'd like
A more logical error code scheme, with digit 1 representing the module (e.g. passgen, phrasegen), digit 2 representing the type of error (e.g. data type validation, file error) and digit 3 being an identifier for the specific error.

For example, rather than [206] for "Password length must be given as an integer.", use a code like [101]

  • 1 - passgen
  • 0 - data type validation
  • 1 - error 1

Describe alternatives you've considered
While the current numbering scheme is okay, the 2 prefix holds no value and is simply used for all error codes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions