Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quality Error reporting #11

Open
BenWeber42 opened this issue Jun 17, 2020 · 1 comment
Open

Quality Error reporting #11

BenWeber42 opened this issue Jun 17, 2020 · 1 comment
Labels
large Requires large effort/time low-prio Low priority issue/task tech-debt Technical debt that is overdue

Comments

@BenWeber42
Copy link
Contributor

There has been no focus on good and human readable error messages so far. Attempts have been made to allow good solutions in the future, but they are very incomplete currently.

@BenWeber42 BenWeber42 added low-prio Low priority issue/task polish Will make the project more polished labels Jun 17, 2020
@BenWeber42 BenWeber42 changed the title Error messages Quality Error reporting Jun 17, 2020
@BenWeber42
Copy link
Contributor Author

This will probably also require a complete overhaul of the exception hierarchy, so errors can be classified into categories such as grammar errors, semantic errors, internal errors, etc.

Infrastructure and utility will probably be needed to support better error reporting. E.g., the transform decorator could help in error reporting.

@BenWeber42 BenWeber42 added large Requires large effort/time tech-debt Technical debt that is overdue and removed polish Will make the project more polished labels Jan 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
large Requires large effort/time low-prio Low priority issue/task tech-debt Technical debt that is overdue
Projects
None yet
Development

No branches or pull requests

1 participant