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

Relative JSON Pointers #34

Open
Julian opened this issue Jan 5, 2019 · 3 comments
Open

Relative JSON Pointers #34

Julian opened this issue Jan 5, 2019 · 3 comments

Comments

@Julian
Copy link

Julian commented Jan 5, 2019

Hi!

Was wondering what you think about @handrews' Relative JSON Pointer specification.

Do you feel it has a place within this library, or would you rather it be separate?

(I ask of course because as in #20, I'm about to add support for validating relative JSON pointers to jsonschema).

Cheers,
-J

@st31ny
Copy link

st31ny commented May 22, 2019

As far as I can see from the specs, relative JSON pointers and ordinary JSON pointers can clearly be distinguished based on their first character, so an extension to this library should be possible.

@handrews
Copy link

@steinymity yes the intention of the original author (I just took it over to update it- it will get a new draft shortly which fixes a typo or two but nothing major) was that they were never ambiguous.

@st31ny
Copy link

st31ny commented May 23, 2019

Well, so the only big hassle I see here is that relative JSON pointers need to be able to go to a parent object/array, but this "feature" is not available on standard dicts.

Maybe it makes sense to split the JSON pointer implementation in a data structure agnostic part (which just does parsing and validation) and an extendible part for a particular data structure, similar to pathlib's PurePath vs Path (and their subclasses).

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

3 participants