Replies: 4 comments
|
I added a PR that addresses this. Could you please review, and merge it if it is acceptable? Thanks! |
0 replies
|
I just added a license to the https://github.com/yalp/jsonpath project. Sorry for the delay... |
0 replies
|
Thanks @yalp! Greatly appreciated. @gavv, what are your thoughts on proceeding? It sounds like @yalp is indicating one should use https://github.com/PaesslerAG/jsonpath going forward (https://github.com/yalp/jsonpath/blob/master/README.md). |
0 replies
|
We could switch but we should solve the compatibility issues first.. See my comment at #49. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
We love
httpexpect, and are using it in our project. However, currentlyhttpexpectdepends ongithub.com/yalp/jsonpathwhich does not come with a license. From a legal standpoint, this is a big red flag, and we need a solution for us to be able to usehttpexpect.Someone raised this issue directly on the
jsonpathrepo (yalp/jsonpath#3), but there has been no movement.Can
httpexpectremove thejsonpathdependency so that we can use this legally? One possibility might be to use another one like https://github.com/PaesslerAG/jsonpath which is licensed under BSD-3. Thoughts?All reactions