-
Upgrading from 1.1.9 to 1.2.0+ causes REST responses of `application/json` contentType to return charset: `application/json; charset=utf-8` instead of just `application/json`. This causes client libr…
-
Suggestion to discuss (and plan) a future option to store tags and other attributes in a unique and flexible [JSONB](http://www.postgresql.org/docs/9.5/static/datatype-json.html) field.
Typical case…
-
`LoaderAndLayerInterface.md` does not really define `"layer"`. But in `VkLayer_multi.json`, each layer is started by a `"layer"`. According to RFC 7159,
```
The names within an object SHOULD be uni…
-
Our new JSON (as the old JSON) currently uses escape sequences for characters outside the base ASCII range (a default setting of [`json.dump`](https://docs.python.org/2/library/json.html#basic-usage) …
-
Let's just start by sticking some vocabulary so we speak the same language:
- JSON is plain ASCII. Non ASCII characters are escaped as a sequence of ASCII characters as unicode codepoints like \uxxxx.…
-
Return a complex JSON having a long-value of -1369082024195183657 resolves in illegal JSON.
```
{ id:20,
data:{
name: 'max',
age: 21,
hash: -1369082024195183657
}
}
```
But in brows…
-
``` json
schema =\
{ "definitions":
{ "properties":
{ "p1":
{ "type": "string"
}
, "p2":
{ "type": "integer"
…
-
Section 8.3 says:
> P4 compilers should handle correctly UTF-8 characters in comments and string literals.
Appendix 23 says:
> The STRING_LITERAL token corresponds to a doubly-quoted string contai…
-
RFC4627 says in Sect. 2 that valid json must be either an object or array at the root:
```
JSON-text = object / array
```
following the ABNF definitions in RFC4627, this means that it must start wit…
-
Dear Developer,
i´ve tested you´re code which is great but, in one case it´s not round up JSON / REST technology.
If you create a new entity with post you will get as return an integer with the new i…