diff --git a/docs/html/md__schemas.html b/docs/html/md__schemas.html
index aee2bd096b8..f7c39efb17d 100644
--- a/docs/html/md__schemas.html
+++ b/docs/html/md__schemas.html
@@ -153,6 +153,7 @@
JSON Parsing
- It accepts field names with and without quotes, like many JSON parsers already do. It outputs them without quotes as well, though can be made to output them using the
strict_json
flag.
- If a field has an enum type, the parser will recognize symbolic enum values (with or without quotes) instead of numbers, e.g.
field: EnumVal
. If a field is of integral type, you can still use symbolic names, but values need to be prefixed with their type and need to be quoted, e.g. field: "Enum.EnumVal"
. For enums representing flags, you may place multiple inside a string separated by spaces to OR them, e.g. field: "EnumVal1 EnumVal2"
or field: "Enum.EnumVal1 Enum.EnumVal2"
.
+- Similarly, for unions, these need to specified with two fields much like 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.
When parsing JSON, it recognizes the following escape codes in strings:
diff --git a/docs/source/Schemas.md b/docs/source/Schemas.md
index 1329f9ee209..7f8b0a14495 100755
--- a/docs/source/Schemas.md
+++ b/docs/source/Schemas.md
@@ -298,6 +298,10 @@ JSON:
representing flags, you may place multiple inside a string
separated by spaces to OR them, e.g.
`field: "EnumVal1 EnumVal2"` or `field: "Enum.EnumVal1 Enum.EnumVal2"`.
+- Similarly, for unions, these need to specified with two fields much like
+ 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.
When parsing JSON, it recognizes the following escape codes in strings: