DevFW-CICD/garm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
garm/vendor/github.com/go-openapi/jsonpointer
History
Gabriel Adrian Samfira 0093393bc3 Update all dependencies 
Note: should we ditch vendoring?

Signed-off-by: Gabriel Adrian Samfira <gsamfira@cloudbasesolutions.com>
2025-09-29 13:30:24 +03:00
..
.editorconfig Generate initial swagger API client library code 2023-06-30 19:04:13 +03:00
.gitignore Generate initial swagger API client library code 2023-06-30 19:04:13 +03:00
.golangci.yml Update all dependencies 2025-09-29 13:30:24 +03:00
CODE_OF_CONDUCT.md Generate initial swagger API client library code 2023-06-30 19:04:13 +03:00
errors.go Update all dependencies 2025-04-17 18:07:33 +03:00
LICENSE Generate initial swagger API client library code 2023-06-30 19:04:13 +03:00
pointer.go Update all dependencies 2025-09-29 13:30:24 +03:00
README.md Update all dependencies 2025-09-29 13:30:24 +03:00

README.md

gojsonpointer Build Status codecov

Slack Status license Go Reference Go Report Card

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

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 "-".