kql: only allow top() at start of selector #388
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Maybe we can add some explanatory text as well, to clarify that |
|
Yes you're right, I have added an explanation. |
zkat
approved these changes
Apr 16, 2024
|
lgtm, I'll let @larsgw have an eyeball at it since he was part of our discussion, too. |
|
I'd rather have |
|
I have renamed the rules as suggested. |
larsgw
approved these changes
Apr 17, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
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.
Following discussion #387, I propose a change to the KQL grammar. With this change,
top()will only be allowed at the start of a KQL selector.