Refactor KQL parsing to follow a forward order#242
Draft
ltrk2 wants to merge 386 commits intoKusto-phase3from
Draft
Refactor KQL parsing to follow a forward order#242ltrk2 wants to merge 386 commits intoKusto-phase3from
ltrk2 wants to merge 386 commits intoKusto-phase3from
Conversation
Co-authored-by: ltrk2 <107155950+ltrk2@users.noreply.github.com>
…on on every evaluated ip
implementation of has_ipv4, has_any_ipv4, has_ipv4_prefix, and has_an…
add release notes
kashwy
force-pushed
the
Kusto-phase3
branch
from
36d6fe2 to
61e14cd
Compare
kothiga
force-pushed
the
Kusto-phase3
branch
2 times, most recently
from
1e1f94f to
3fab19c
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Refactor KQL to follow a forward order