-
Notifications
You must be signed in to change notification settings - Fork 465
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
wrong line in error message #972
Comments
@mgreter any ideas here? |
Whitespace was not "actively" lexed, so position still points to the position it is reporting. Maybe we should move the parser when an error is thrown (we attach the prefixed whitespace to each lexed token, so we should not just munch away whitespace on it own). |
OK, the actual bug is caused by the way |
Are you sure this is fixed? I'm still getting the wrong line reported… |
I was pretty sure it was fixed, but it looks you're correct => #1002 |
Added a new commit which will hopefully solve it now (8d8dc08)! |
Considering the following (invalid) input:
I get the error reported on line 5 (
3.2.1-beta.2
) and the formatted error message looks as follows:3.1.0
reports the error on line 7The text was updated successfully, but these errors were encountered: