We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Awesome, thanks for the quick response.
I published an updated table. There seems to be a regression that slipped in, see https://github.com/cburgmer/json-path-comparison/blob/master/comparison/results/wildcard_bracket_notation_on_array.md. If you are interested, I'm planning on compiling a consumable test set, possibly as a YAML artefact for library authors to consume and integrate (see https://github.com/cburgmer/json-path-comparison#roadmap).
Originally posted by @cburgmer in #6 (comment)
The text was updated successfully, but these errors were encountered:
Invalid wildcard filter results #7
6d38c67
Invalid wildcard filter results #7 - nodejs, wasm
967df1b
f1fda2a
No branches or pull requests
Awesome, thanks for the quick response.
I published an updated table.
There seems to be a regression that slipped in, see https://github.com/cburgmer/json-path-comparison/blob/master/comparison/results/wildcard_bracket_notation_on_array.md. If you are interested, I'm planning on compiling a consumable test set, possibly as a YAML artefact for library authors to consume and integrate (see https://github.com/cburgmer/json-path-comparison#roadmap).
Originally posted by @cburgmer in #6 (comment)
The text was updated successfully, but these errors were encountered: