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

Make Errors more useful #2

Open
letmutx opened this issue Nov 12, 2019 · 0 comments
Open

Make Errors more useful #2

letmutx opened this issue Nov 12, 2019 · 0 comments

Comments

@letmutx
Copy link
Owner

letmutx commented Nov 12, 2019

Goal: To be able to pin-point a location where the malformed input is/error occurs.

Currently the Error type doesn't contain information on where an error happened. I think it'd be helpful if we have at least these details to start with:

  • Class name/ClassId - the error occurred while reading this Class from the input.
  • Method/Field - if relevant.
  • Id's of items (say in string_ids, type_ids section etc.)
@letmutx letmutx changed the title Make Errors more useful Make Errors more useful Nov 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@letmutx