Added support for parsing JSON null value.

These cause the field in question to be skipped.

Bug: 16550393
Change-Id: Id05104e89818ee773b8a91fdcc86e18061b9a82f
Tested: on Linux.
This commit is contained in:
Wouter van Oortmerssen
2016-01-08 15:18:51 -08:00
parent e848137ded
commit 049f3f7907
4 changed files with 30 additions and 16 deletions

View File

@@ -313,6 +313,9 @@ JSON:
you do when serializing from code. E.g. for a field `foo`, you must
add a field `foo_type: FooOne` right before the `foo` field, where
`FooOne` would be the table out of the union you want to use.
- A field that has the value `null` (e.g. `field: null`) is intended to
have the default value for that field (thus has the same effect as if
that field wasn't specified at all).
When parsing JSON, it recognizes the following escape codes in strings: