-
Notifications
You must be signed in to change notification settings - Fork 7
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
Parse the wildcard child selector .*
/[*]
#6
Labels
Milestone
Comments
.*
.*
/`..*
.*
/`..*.*
/..*
`
.*
/..*
`.*
/..*
This was referenced Sep 15, 2022
.*
/..*
.*
/..*
/.[*]
/..[*]
.*
/..*
/.[*]
/..[*]
.*
/.[*]
This was referenced Jan 21, 2023
V0ldek
added a commit
that referenced
this issue
Jan 22, 2023
Both shorthand `.*` and full `[*]` forms are recognised. Related: #6
.*
/.[*]
.*
/[*]
V0ldek
added a commit
that referenced
this issue
Jan 22, 2023
Both shorthand `.*` and full `[*]` forms are recognised. Related: #6
V0ldek
added a commit
that referenced
this issue
Jan 28, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your feature request related to a problem? Please describe.
The wildcard child selector should be recognized by the parser and parsed into an appropriate
JsonPathQueryNode
. Note that this means both the.*
and[*]
patterns, selecting any child. The index and non-index version have identical semantics.Describe the solution you'd like
There are two possible solutions.
Label
into a variant type and have a variant for the wildcard.AnyChild
.It's not obvious to me which one is better. Approach 2 seems to be a little easier to do, since it won't have to touch the widely used
Label
type.The consumers of queries should react to the new variant with an error "not supported yet".
Additional context
Find the syntax for the selectors in the RFC:
The text was updated successfully, but these errors were encountered: