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.

Sign up for GitHub

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

Jump to bottom

Implement pretty_errors feature #19

Closed
Tracked by #31
Emoun opened this issue Sep 27, 2020 · 2 comments
Closed
Tracked by #31

Implement pretty_errors feature #19

Emoun opened this issue Sep 27, 2020 · 2 comments
Labels
D-accepted A decision (D) has been made and the issue will be worked on I-feature This issue (I) regards a (potential) feature in the project T-accepted Triage (T): Initial review accepted issue/PR as valid

Comments

@Emoun
Copy link
Owner

Emoun commented Sep 27, 2020

Currently we have a feature called pretty_errors that is intended to give better error messages than without the feature.

This is currently only haphazardly implemented and not automatically tested.
We should therefore add a setup that tests the error messages provided by this feature.
@Emoun Emoun added I-feature This issue (I) regards a (potential) feature in the project T-accepted Triage (T): Initial review accepted issue/PR as valid labels Sep 27, 2020
@Emoun Emoun mentioned this issue Dec 26, 2021
Closed
12 tasks
@Emoun Emoun added the D-accepted A decision (D) has been made and the issue will be worked on label Feb 26, 2023
@Emoun
Copy link
Owner Author

Emoun commented Feb 26, 2023

Work has started on this as of the completion of #30.

@Emoun
Copy link
Owner Author

Emoun commented Mar 9, 2023

pretty_errors is now as well tested as the basic error reporting.
There are still many cases to handle, but pretty_errors is no longer less well implemented than the basic error reporting.
The reporting for further cases still needs work, but this issue has been solved in the sense that pretty_errors now provides the benefits it was intended for, even though error reporting in general can still be worked on.

@Emoun Emoun closed this as completed Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
D-accepted A decision (D) has been made and the issue will be worked on I-feature This issue (I) regards a (potential) feature in the project T-accepted Triage (T): Initial review accepted issue/PR as valid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Emoun