We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Expected behavior Valid queries should not raise a a parse error. It runs as expected in Power BI.
Actual behavior
Expected to find a right brace <'}'>, but a keyword <'in'> was found insteadpowerquery(Error.Parse)
To Reproduce: Case 1
let start = 0, end = 10, sequence = {start..end} in sequence
To Reproduce: Case 2
let start = 10, Numbers = {start..10} in Numbers
Expected to find a right brace <'}'>, but a numeric literal was found insteadpowerquery(Error.Parse)
Working case
let end = 10, Numbers = {0..end} in Numbers
The text was updated successfully, but these errors were encountered:
Found the issue. It's that the lexer is generating an identifier token start. which shouldn't be valid, as identifiers do not allow trailing commas.
start.
Sorry, something went wrong.
Bugfix #186 - Identifiers shouldn't end with a period (#187)
453045c
* initial commit * fixed edge case, added tests
JordanBoltonMN
No branches or pull requests
Expected behavior
Valid queries should not raise a a parse error. It runs as expected in Power BI.
Actual behavior
To Reproduce: Case 1
To Reproduce: Case 2
Working case
The text was updated successfully, but these errors were encountered: