Skip to content
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

Consider using CWJSONPointer for path tree #4

Open
grgcombs opened this issue Apr 11, 2014 · 4 comments
Open

Consider using CWJSONPointer for path tree #4

grgcombs opened this issue Apr 11, 2014 · 4 comments

Comments

@grgcombs
Copy link
Contributor

There's an Objective-C project that implements the JSONPointer spec. Rather than use NSURL to manually navigate down the tree, maybe consider using this JSONPath functionality?

https://github.com/C-Works/NSDictionary-CWJSONPointer

@samskiter
Copy link
Owner

Yes, this was developed at the same time as this library. I would be interested to see it used in this project

@samskiter
Copy link
Owner

Hmm. I've recently submitted this PR to the JSON-Schema-Test-Suite: json-schema-org/JSON-Schema-Test-Suite#65 And I don't believe this library will pass the new test in it's current state.

I think the solution to this will be to look for 'id' tags during resolution. As a result we may have to continue to use our own JSON pointer resolution implementation

@grgcombs
Copy link
Contributor Author

grgcombs commented Nov 3, 2014

I put together a derivative JSONPointer implementation in JSONTools. I've fixed up a few issues that affect CWJSONPointer, and I think this may be one I resolved (I'm not certain, though -- I'll review).

@samskiter
Copy link
Owner

I don't believe resolution context changes via the 'id' property are a part
of JSON pointer are they?
On 3 Nov 2014 14:43, "Greg Combs" [email protected] wrote:

I put together a derivative JSONPointer implementation in JSONTools. I've
fixed up a few issues that affect CWJSONPointer, and I think this may be
one I resolved (I'm not certain, though -- I'll review).


Reply to this email directly or view it on GitHub
#4 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants