-
-
Notifications
You must be signed in to change notification settings - Fork 55
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 does not apply to object fields when wildcard used #64
Comments
Currently, in JsonSurfer the filter is supported for array structure only. There is not an official standard for JsonPath syntax for now. You can check the differences among JsonPath projects in this repo: https://github.com/cburgmer/json-path-comparison |
We ran into the same issue. It would be awesome if this can be supported. A second very similar case we encountered: to objects of the same name (instead of using an array). Seems to be a valid json too (at least jackson can process it). "a": { instead of: "a": [ See also cburgmer/json-path-comparison#41 |
Steps to reproduce
Example JSON:
Queries:
Code:
Expected
The queries
$.*[?(@.size > 13)]
and$[?(@.size > 13)]
return an array of two items:Actual
Both queries return an empty array:
Note
The queries
$.*
and$[*]
return an array of all three items:So I would expect that a filter after a wildcard is working fine.
Environment
JsonSurfer 1.6.0 + Jackson Parser + Jackson Provider.
The text was updated successfully, but these errors were encountered: