-
there's probably nothing else to do other than updating the reference to the latest JSON RFC.
-
https://www.rfc-editor.org/rfc/rfc8259.txt
-
Problem: as discussed in flux-framework/flux-sched#938, encoding 64-bit job IDs as JSON numbers could present an interoperability problem as some JSON implementations represent all numbers as IEEE 764…
-
Before submitting an issue, please ensure that you have read the documentation:
* Basics is an overview of how to use simdjson and its APIs: https://github.com/simdjson/simdjson/blob/master/doc/bas…
-
All tests from [nst/JSONTestSuite](https://github.com/nst/JSONTestSuite) with a single value (string, number, boolean, or null) at the root fail with an error:
```
document root must be object or ar…
-
When dealing with incomplete JSON, the `(*Decoder).Token` method returns `io.EOF` at the end of the input instead of providing an appropriate error. For example, the following code does not produce an…
-
There are some underlying principles that the JSON Schema project has been based on, but we've never really written them out. A concise list would be appropriate in the Core spec, as they might head …
-
The presence of duplicate fields in JSON input is almost always a bug from the sender and the behavior across various implementations is highly inconsistent. It's too late to switch the current behavi…
dsnet updated
12 months ago
-
plist_from_json() fails when encountering JSON number tokens containing explicit positive exponents "e+" or "E+" followed by the exponent digits. It does work for "e-", "E-", "e", and "E". The curre…
sctol updated
4 months ago
-
JSON produced by `ConstraintSet$WriteJsonEngine` from method `ConstraintSet#writeState(0)` does not follows RFC 8259 or 4627 standards.
For example in WriteJsonEngine as key punctuators used single…