-
Notifications
You must be signed in to change notification settings - Fork 147
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
User defined function in custom namespace parsed as property lookup if function name is a keyword #552
Comments
I think it is related to this part of the grammar:
For |
I am also seeing a flavor of this issue for
with 'CREATE' being a reserved word. |
From what I can see in the 'User-defined functions' section of the specification v9, there is no restriction on function names or namespaces containing reserved words. This does seem like an issue with the grammar. |
We've encountered an issue where we name a user defined function to a keyword.
For example
Is parsed as a property lookup of property
all
on objectmyns
. It seems this is related toALL
being a keyword. It parses correctly for all function names except when using keywords as function names.Just wanted to check if there is a rule that you cannot name any functions within user defined namespaces to keywords or if there is a bug somewhere?
We are using antlr4 for JavaScript to do the parsing.
The text was updated successfully, but these errors were encountered: