mirror of https://git.kore.io/kore.git
9cfcd9a4be
- Try harder to mark integers as KORE_JSON_TYPE_INTEGER, especially if they fit in the internal representation of one (int64_t). - Move error codes into the JSON code itself, rather then requiring a kore_json data structure. This allows the JSON API to relay errors such as "item not found" or "type mismatch" properly when looking at items. - When asking for a KORE_JSON_TYPE_INTEGER_U64 and a KORE_JSON_TYPE_INTEGER was found with the same name, check if it could be returned properly and do so if possible. |
||
|---|---|---|
| .. | ||
| conf | ||
| src | ||
| .gitignore | ||
| README.md | ||
README.md
Native Kore JSON parser example.
Run:
$ kodev run
Test:
$ curl -i -k -d '{"foo":{"bar": "Hello world"}}' https://127.0.0.1:8888
The result should echo back the foo.bar JSON path value if it is a JSON string.