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

Better parsing errors #9

Closed
JimmyCushnie opened this issue Mar 30, 2019 · 1 comment
Closed

Better parsing errors #9

JimmyCushnie opened this issue Mar 30, 2019 · 1 comment
Labels
feature/enhancement New feature or request

Comments

@JimmyCushnie
Copy link
Owner

Parsing errors currently only tell you what kind of error happened. Sometimes they quote you the part of the file that caused the error. Every time a parsing error is thrown, the following information should be included:

  • the full path of the file
  • the line number on which the error occurred

Parsing errors should probably be their own kind of exception as well.
@JimmyCushnie JimmyCushnie added the feature/enhancement New feature or request label Mar 30, 2019
@JimmyCushnie JimmyCushnie mentioned this issue Feb 3, 2022
Merged
@JimmyCushnie
Copy link
Owner Author

Implemented in #38 :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature/enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JimmyCushnie