-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
fix(ingest/powerbi): support each expression in m-query function invocation #7541
Changes from all commits
8b44bad
32e0e83
eaed073
9a52071
7c5989e
991649b
a1daae3
67e28fd
5d2af5b
21a1589
d0c0654
bbd33aa
c97aaa6
3d420d8
7c44c34
8e5128e
f4d5216
bb031b9
4573048
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,9 @@ | |
// - The let_expression definition has added the whitespace rule instead of the required newline. | ||
// This allows the parser to be less strict about whitespace. | ||
// - Add inline whitespace to item_selection and optional_item_selection. | ||
// - Tweak unary_expression to allow arbitrary operators within it. | ||
// This is necessary because unary_expression is the base for the | ||
// whole relational_expression parse tree. | ||
|
||
|
||
lexical_unit: lexical_elements? | ||
|
@@ -302,6 +305,7 @@ unary_expression: type_expression | |
| "+" unary_expression | ||
| "_" unary_expression | ||
| "not" unary_expression | ||
| expression | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. nice - so this broadens the definition so that unary expression can be any type of expression? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yep - this isn't strictly correct because it can cause incorrect order of operations in the AST (e.g. addition before multiplication or something), but we don't really care about that here |
||
|
||
primary_expression: literal_expression | ||
| list_expression | ||
|
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.
What was the previous assert doing here? No purpose?
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.
this broadens it from quoted_identifier -> identifier (which includes regular_identifier)