-
Notifications
You must be signed in to change notification settings - Fork 73
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
Results do not match other implementations #115
Comments
Interesting. I'll take a look. Some of these are definitely weird. |
One thing though. This: |
So. We are also returning the keys basically, not just the values in case of That would break the current usage pattern of this gem which people using it rely upon. If people would like to have other types of results, I suggest to use a different gem. I don't see this a bug. :) It's a feature of this gem to also include the keys in the results. If you happen to find an inconsistency which shows up as a bug, please report that separately. Thank you! |
Thanks for your response. |
Absolutely please do so. And thank you for the issue and your time. 😊 |
The following queries provide results that do not match those of other implementations of JSONPath
(compare https://github.com/cburgmer/json-path-comparison/tree/master/comparison):
$[1:10]
Input:
Expected output:
Actual output:
$['0']
Input:
Expected output:
Actual output:
$..*
Input:
Expected output:
Actual output:
$.*
Input:
Expected output:
Actual output:
$.*
Input:
Expected output:
Actual output:
For reference, the output was generated by the program in https://github.com/cburgmer/json-path-comparison/tree/master/implementations/Ruby_jsonpath.
The text was updated successfully, but these errors were encountered: