Provide an API for detecting invalid JSON Pointers

Question

Provide an API for detecting invalid JSON Pointers

Julian opened this issue 8 years ago · 5 comments

Hi!

Would you consider an API to validate whether a particular input was valid under RFC 6901 (or does such a thing exist already and I've missed it)?

E.g., /foo/bar~ is not a valid JSON Pointer seemingly (the ~ is not escaped), but I cannot see an API that complains about that -- jsonpointer.JsonPointer will happily accept it as another pointer part.

(Even having jsonpointer.JsonPointer do enough validation of its inputs would also work).

Full context: JSON Schema Draft 6 adds a jsonpointer format. I'd love to use python-json-pointer to implement it in jsonschema.

Answer 1 · 2017-10-28T10:49:43.000Z

JsonPointer is already doing some form of input validation (eg it complains if there is no leading /). I've now extended this for the cases you mentioned in #24.

Can you please have a look if this would meet your requirements?

Answer 2 · 2017-10-29T18:25:01.000Z

Hey! Thanks, that does work, and passes all the tests. Appreciated!

Answer 3 · 2017-10-30T19:50:47.000Z

I've just released version 1.14 with the new validations.

Answer 4 · 2017-10-30T19:56:04.000Z

Awesome! Will have a look, thanks so much!

…

On Oct 30, 2017 15:50, "Stefan Kögl" ***@***.***> wrote: I've just released version 1.14 with the new validations. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#20 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAUIXuV1HhfqbXONoURuDrchEf9UY9SFks5sxiiXgaJpZM4N9TD4> .

Answer 5 · 2017-11-08T23:57:32.000Z

Just confirming, looks spot on, thanks again.

Hoping to push out a jsonschema release with Draft 6 support containing it in the next few weeks.