-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
Replace github.com/yalp/jsonpath with github.com/PaesslerAG/jsonpath #49
Conversation
Thanks. LGTM, but I think I need to test it a bit before merging to ensure that we don't break compatibility. |
Thanks. Absolutely. |
Hi, sorry for delay. I've added some tests for jsonpath (based on original yalp/jsonpath tests): Unfortunately, this small PR breaks the compatibility. Below you can find the list of cases where yalp/jsonpath and PaesslerAG/jsonpath work differently. Test JSON:
You can check these cases using this online tester: https://codebeautify.org/jsonpath-tester. So what we have so far:
I'm not sure if the first two features are standard, but if we reject them we will break the compatibility. So we have several options:
|
All bugs I've found in yalp/jsonpath are now fixed in upstream. Since it also has a LICENSE file, I guess there is no urgency now to make a switch. On the other hand, all important JSONPath features are now covered with httpexpect tests, so making a switch would be safe. Switching to PaesslerAG/jsonpath makes sense since it seems to be a more complete implementation. However, compatibility issues should be addressed first. If someone is interested, pull requests are welcome. |
Closing this for now. |
Fix #48.
It replaces the github.com/yalp/jsonpath dependency which does not have a license with github.com/PaesslerAG/jsonpath.