-
Notifications
You must be signed in to change notification settings - Fork 5
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
Predicate on our "well-known attributes" #113
Merged
Merged
Changes from all commits
Commits
Show all changes
26 commits
Select commit
Hold shift + click to select a range
271b464
Refactored Attribute to data::AttributeValue
alexsnaps 762091d
Refactored property stuff to data::property
alexsnaps 78d5eb0
Refactored using PropertyPath everywhere
alexsnaps 7624900
Refactored using AttributeValue everywhere
alexsnaps 54ad632
ports are u64, not strings... this err'ed into Default
alexsnaps eede19a
Slowly getting there
alexsnaps 222a7cf
Wired the base
alexsnaps f4fd18f
Clippy fixes
alexsnaps 34c7050
Notes for auth/json integration
alexsnaps df48e11
Typos and test infra for hostcalls::get_property
alexsnaps 8c001f3
Predicate test
alexsnaps ce49eb2
Transparently replace PatternExpression with CEL Predicate
alexsnaps 60820e0
Moar clippy
alexsnaps 067aaf2
Deal with unknown attributes as JSON literals
alexsnaps 06000e0
Arguable: but lets fall back to string on bad json
alexsnaps 7dc7ac9
wasm props are in the filter_state
alexsnaps 611a900
Deal with more types & json encode values
alexsnaps f911798
Have auth in wasm prop and log on unexpected type
alexsnaps dbdf7e1
Deal with previously resolved values on path digging into these
alexsnaps 5deae3b
Don't warn on structs when storing values as json
alexsnaps a786e94
Support headers in CEL
alexsnaps 00d4863
Remove trailing comment
alexsnaps b63057f
No more dead code
alexsnaps b9af3dc
Support for CEL expressions in data exports
alexsnaps 7528942
request.time is a Timestamp
alexsnaps 06cd03d
README reflecting new config
alexsnaps File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
can we make
key
optional? it would default to the expression value (not the referenced value, though).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.
I think it makes for a very horrible default, but... 🤷