-
Notifications
You must be signed in to change notification settings - Fork 41
Provide an API for detecting invalid JSON Pointers #20
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
Comments
JsonPointer is already doing some form of input validation (eg it complains if there is no leading Can you please have a look if this would meet your requirements? |
Hey! Thanks, that does work, and passes all the tests. Appreciated! |
I've just released version 1.14 with the new validations. |
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>
.
|
Just confirming, looks spot on, thanks again. Hoping to push out a |
Uh oh!
There was an error while loading. Please reload this page.
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.
The text was updated successfully, but these errors were encountered: