46534309e6
The whole point of an alternate is to allow some type-safety while still accepting more than one JSON type. Meanwhile, the 'any' type exists to bypass type-safety altogether. The two are incompatible: you can't accept every type, and still tell which branch of the alternate to use for the parse; fix this to give a sane error instead of a Python stack trace. Note that other types that can't be alternate members are caught earlier, by check_type(). Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <1455778109-6278-4-git-send-email-eblake@redhat.com> [Commit message tweaked] Signed-off-by: Markus Armbruster <armbru@redhat.com>
5 lines
133 B
JSON
5 lines
133 B
JSON
# we do not allow the 'any' type as an alternate branch
|
|
{ 'alternate': 'Alt',
|
|
'data': { 'one': 'any',
|
|
'two': 'int' } }
|