-
[RFC 6901](https://tools.ietf.org/html/rfc6901#section-4) requires that when evaluating a JSON pointer expression, the values `~0` and `~1` must be unescaped to `~` and `/` respectively. swagger-parse…
-
Consider adding support for JSON Pointer. The RFC is at [http://tools.ietf.org/html/rfc6901](http://tools.ietf.org/html/rfc6901)
-
tl;dr JSON Patch paths should have `/` & `~` escaped with `~1` & `~0` respectively, see http://tools.ietf.org/html/rfc6901#section-4 for more details on what's required.
I've submitted a [PR](https:/…
-
What do you think about adding [JSON Pointer](https://tools.ietf.org/html/rfc6901#section-5) support to the library?
From the API point of view I think it would mean a new method with a signature lik…
erosb updated
8 years ago
-
If I read [RFC 6901](https://tools.ietf.org/html/rfc6901) correctly (and I'm slightly RFC impaired), the colon character `:` should be OK to use in JSON pointers. However, `json-schema-2.6.1` will bre…
-
JsonPatch and more so RFC 6901 (http://tools.ietf.org/html/rfc6901) allows for the use of "-" to denote a position after the last position of an array. This is important as at the moment the library o…
-
when the library is being used in a web application and want it to look a reference from the application root in a json which was referenced, the library doubles the context on uri.
I have this probl…
-
According to RFC 6901 Section 3, forward slashes in references are encoded as ~1.
See: https://tools.ietf.org/html/rfc6901
In my use case this means:
```
paths:
/account/token:
$ref: 'paths/a…
-
Sensitive information #62 is redacted.
By convention sensitive information is any property whose name starts with a `~`.
-
Jira issue originally created by user dunglas:
I plan to add support for JSON Pointer (RFC 6901: http://tools.ietf.org/html/rfc6901) and JSON Patch (RFC 6902: http://tools.ietf.org/html/rfc6902) synt…