Changes param in cmd-parser to take escaped strings too #309
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cypher5/25Parser.g4 define
parameter[String paramType]
: DOLLAR parameterName[paramType]
;
parameterName[String paramType]
: (symbolicNameString | UNSIGNED_DECIMAL_INTEGER)
;
In CypherCmdParser.g4 instead we had:
paramsCmd: PARAM paramsArgs?;
paramsArgs: (CLEAR | listCompletionRule | map | lambda);
lambda: unescapedSymbolicNameString EQ GT expression;
So params created with lambda could never be escaped, even though regular parser allows it. this aligns cmd-parser with regular.