You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a test case like this: | setfields test="testtestest", fuu="fuu byr"
it doesn't parse the part after the comma and it gives an error:
line 46:32 mismatched input 'fuu' expecting {PIPE, COMMA}
When looking at the parse tree made from this query, it can be seen that the comma in between two setfieldsParameters is included in the "testtesttest", string. For adding multiple setfieldsParameters, the grammar requires a comma in between, which now there isn't. The parsing is stopped, and only one setFieldsParameter is therefore parsed.
Expected behavior
Should parse multiple setFieldsParameters.
How to reproduce
Test the query above.
Screenshots
Software version
6.1.0
Desktop (please complete the following information if relevant):
OS:
Browser:
Version:
Additional context
Comma isn't an allowed character in a String in setfields, so it is weird that it is parsed as a part of the StringType. More investigation needed for finding the exact culprit of the issue.
setfieldsSyntaxParseTest in SetfieldsSyntaxTests.java has been disabled because of this issue in PR #52.
The text was updated successfully, but these errors were encountered:
Describe the bug
There is a test case like this:
| setfields test="testtestest", fuu="fuu byr"
it doesn't parse the part after the comma and it gives an error:
When looking at the parse tree made from this query, it can be seen that the comma in between two setfieldsParameters is included in the
"testtesttest",
string. For adding multiple setfieldsParameters, the grammar requires a comma in between, which now there isn't. The parsing is stopped, and only one setFieldsParameter is therefore parsed.Expected behavior
Should parse multiple setFieldsParameters.
How to reproduce
Test the query above.
Screenshots
Software version
6.1.0
Desktop (please complete the following information if relevant):
Additional context
Comma isn't an allowed character in a String in setfields, so it is weird that it is parsed as a part of the StringType. More investigation needed for finding the exact culprit of the issue.
setfieldsSyntaxParseTest in SetfieldsSyntaxTests.java has been disabled because of this issue in PR #52.
The text was updated successfully, but these errors were encountered: