-
Notifications
You must be signed in to change notification settings - Fork 8
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
Filter selector – existential filters [?@<path>]
#154
Labels
acceptance: go ahead
Reviewed, implementation can start
area: selector
Support for a JSONPath selector
type: feature
New feature or request
Milestone
Comments
Tagging @V0ldek for notifications |
V0ldek
changed the title
Filter selector – existential filters
Filter selector – existential filters Jun 14, 2023
[?@<path>]
[?@<path>]
github-actions
bot
added
acceptance: go ahead
Reviewed, implementation can start
and removed
acceptance: triage
Waiting for owner's input
labels
Jun 15, 2023
V0ldek
added a commit
that referenced
this issue
Feb 28, 2024
This is mainly an `rsonpath-syntax` change – the selectors are parsed, but `rq` will give you an unsupported error and a link to #154 if you put them in a query.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
acceptance: go ahead
Reviewed, implementation can start
area: selector
Support for a JSONPath selector
type: feature
New feature or request
Is your feature request related to a problem? Please describe.
Support for filters with the following restrictions:
So strictly filters of the form
[?@<path>]
.Describe the solution you'd like
The solution requires a theoretical write-up and then implementation.
The current idea is to have a second DFA, the filter automaton, controlled by the main query automaton. The state of the filter automaton would determine if a given path match is to be emitted, ingored, or stored to potentially be emitted later.
Additional context
RFC draft.
The text was updated successfully, but these errors were encountered: