-
Notifications
You must be signed in to change notification settings - Fork 7
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
Changes param in cmd-parser to take escaped strings too #309
Conversation
|
…main parser does, and modified usage ib parseWrapper to fit
…rized rules are used yet, so I used parameterName["ANY"] for now
41fec4a
to
38948a7
Compare
@@ -60,7 +60,7 @@ export class CypherEditorPage { | |||
} | |||
|
|||
async checkNoNotificationMessage(type: 'error' | 'warning') { | |||
await this.page.waitForTimeout(3000); | |||
await this.page.waitForTimeout(1000); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We haven't found any better alternative than this 😢
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.