-
Consider the following JSON object:
```json
{
"foo": {
"bar": {
"baz": "bat"
}
}
}
```
Using GSON, without registering a custom type adapter, if I want to safely acces…
-
I'd like to suggest adding support for some standard query languages like JSONPath and JSON pointers (RFC 6901) via cmdline switches. e.g.:
`jq --jsonpath "/store/book[1]/title" books.json`
-
### Steps to reproduce the problem
1. Fetch `https://mastodon.social/users/trwnh`
2. Observe the `id` of `publicKey`
### Current behaviour
`https://mastodon.social/users/trwnh#main-key`
#…
-
I've enhance your great package to report errors with [RFC 6901 - JSON Pointer](http://www.rfc-base.org/txt/rfc-6901.txt) for the field name. I published this as [js-schema-6901](https://www.npmjs.co…
-
**Compilation of internet standards (adopted or drafted) that should be taken in account**
- [ ] IP Version 6 Addressing Architecture [RFC 3513](http://tools.ietf.org/html/rfc3513)
- [ ] DOMAIN NAMES…
-
I wrote a package that has a similar aim (better JSON error location reporting) but using JSON Pointer (RFC 6901) and using a wrapper strategy instead of forking. See [github.com/dolmen-go/jsonptrerro…
-
### Go version
go version go1.22.0 darwin/amd64
### Output of `go env` in your module/workspace:
```shell
GO111MODULE=''
GOARCH='amd64'
GOBIN=''
GOCACHE='/Users/alanxu/Library/Caches/go-b…
-
(from an [RFC Errata](http://www.rfc-editor.org/errata_search.php?rfc=6901&eid=3981))
The escape syntax seems weird and confusing. Rather than ~0 and ~1, why not use a repeated (double) slash to esca…
-
JSON Patch specifies that paths be specified in a string format as specified by RFC 6901. This requires additional steps to form paths, first to escape characters (in a new, invented escape not used e…
-
The Target property table in the CS 1.0 Language Spec Section 3.3.1.2 does not include an **example** SLPF target that was included in CSPRD 01, but it still has Actuator (3.3.1.3) and Results (3.3.2.…