0093393bc3
Note: should we ditch vendoring? Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
26 lines
1.5 KiB
Markdown
26 lines
1.5 KiB
Markdown
# gojsonpointer [](https://github.com/go-openapi/jsonpointer/actions?query=workflow%3A"go+test") [](https://codecov.io/gh/go-openapi/jsonpointer)
|
|
|
|
[](https://slackin.goswagger.io)
|
|
[](https://raw.githubusercontent.com/go-openapi/jsonpointer/master/LICENSE)
|
|
[](https://pkg.go.dev/github.com/go-openapi/jsonpointer)
|
|
[](https://goreportcard.com/report/github.com/go-openapi/jsonpointer)
|
|
|
|
An implementation of JSON Pointer - Go language
|
|
|
|
## Status
|
|
Completed YES
|
|
|
|
Tested YES
|
|
|
|
## References
|
|
|
|
<https://tools.ietf.org/html/draft-ietf-appsawg-json-pointer-07>
|
|
|
|
also known as [RFC6901](https://www.rfc-editor.org/rfc/rfc6901)
|
|
|
|
### Note
|
|
|
|
The 4.Evaluation part of the previous reference, starting with 'If the currently referenced value is a JSON array, the reference token MUST contain either...' is not implemented.
|
|
|
|
That is because our implementation of the JSON pointer only supports explicit references to array elements: the provision in the spec
|
|
to resolve non-existent members as "the last element in the array", using the special trailing character "-".
|