-
Notifications
You must be signed in to change notification settings - Fork 6
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
Add support for Level 3 #1
Comments
Hi @therealprologic, funny you should mention it. level 3 is something I plan on implementing this weekend. @latestrevision implemented the level in go, which should be quite transferrable https://github.com/latestrevision/go-jsonselect He also pointed me to this article which I hope should clear things up http://lloyd.io/jsonselect-grows-up In the mean time, don't let me stop you from contributing any fixes you see |
Thats fantastic news, Look forward to it! Sent from my iPad On 28 Nov 2013, at 15:53, Matthew Hooker [email protected] wrote: Hi @therealprologic https://github.com/therealprologic, funny you should mention it. level 3 is something I plan on implementing @latestrevision https://github.com/latestrevision implemented the level He also pointed me to this article which I hope should clear things up In the mean time, don't let me stop you from contributing any fixes you see — |
Hi @mwhooker just wondering if you are still working on this or have lost a bit of interest? Curious more than anything :) |
So I've been trying to work on this but running into several issues:
|
ping @mwhooker |
Since this project seems to have stalled, I've created a new one: pyjsonselect. It's based on the JS reference implementation and hence is fully conformant with all levels of the spec. If you need the level 3 selectors, you may wish to give it a try. |
Hi All, sorry for the radio silence. I'm no longer maintaining this, as there are far better solutions, such as http://www.jsoniq.org/ and https://github.com/boto/jmespath and now @danvk's |
The author [has indicated](mwhooker/jsonselect#1 (comment)) that he's no longer maintaining it.
Awesome! Thanks guys :) I'll check these out! James Mills / prologic E: [email protected] On Tue, Oct 7, 2014 at 10:43 AM, Matthew Hooker [email protected]
|
Adding support for Level 3 would be nice. I plan to evaluate the use of your library in a production project at work. The spec seems fairly clear to me on Level 3 aspects. Not sure on "expressions" though.
The text was updated successfully, but these errors were encountered: