Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.
Sign upBetter syntax mistake errors #372
Comments
This comment has been minimized.
This comment has been minimized.
|
To cover more syntax error cases with custom error messages, we'd need to move away from Lex&Yacc and build our own parser from scratch. That's not likely to happen soon, so unfortunately we'll be stuck with the current level of error reporting for the time being. |
This comment has been minimized.
This comment has been minimized.
|
Fixed by #676 |
fabxc
closed this
May 7, 2015
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
simonpasquier
pushed a commit
to simonpasquier/prometheus
that referenced
this issue
Oct 12, 2017
This comment has been minimized.
This comment has been minimized.
lock
bot
commented
Mar 24, 2019
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
lock
bot
locked and limited conversation to collaborators
Mar 24, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
typingduck commentedNov 11, 2013
Currently syntax errors in the UI are of the form "Error parsing rules at line 1, char 6: syntax error" when the 5th character is incorrect.
The off-by-one error plus not reporting which character is the problem makes it difficult to diagnose.
(As a side not the problem character here was the '.' char. Not sure if this is explicitly disallowed or not. If disallowed then perhaps it should be filtered out at an earlier stage)