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
Alert user to misuse of reserved literals in the rule source editor #7006
Comments
This popped up again in the community. This reproduces all the way up to GL 5.2.
The rule editor UI does not show any error. Clicking the create or update button has no effect. Very frustrating. |
All of these literals from the ANTRL grammar are problematic: Line 127 in ac960a5
That can't be helped. But we should give the user some indication of what the problem is. |
Rulebuilder UI does not have this problem since you can only use existing values as parameters. |
Calling a variable "match" breaks parsing and produces
{"type":"ApiError","message":""}
error response.Expected Behavior
Rule can be parsed and saved
Current Behavior
XHR returns
{"type":"ApiError","message":""}
Server log has
Possible Solution
Should either be accepted or documented or at least show a better error message.
Steps to Reproduce (for bugs)
put this into create rule dialog:
Changing var name to "mach" fixes it.
Context
I was trying to write
let match = regex(...);
Your Environment
The text was updated successfully, but these errors were encountered: