Add func registry support for FilterQL statements. #101
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
| *filterTokenPager | ||
| firstToken lex.Token | ||
|
|
||
| funcs expr.FuncResolver | ||
| } | ||
|
|
There was a problem hiding this comment.
not sure if you like the builder pattern NewFilterParser().Statement(filter).ParseFilter(). we can change it if you don't. I was just trying to reduce the number of constructors.
|
let me pull this and play with it |
|
@araddon cool, feel free to change it however you like :) . |
|
played with it some more local, lgtm merging. ty! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in 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.
When using filter QL for evaluating different domains within the same binary. We need to be able to isolate func resolution to specific subdomains.