Skip to content

empty object in json schema should accept arbitrary json #2005

Description

@1inguini

Empty object {} in json schema should accepts arbitrary json.

I first noticed this behavior in Haskell codegen.
Output from { "additionalProperties": true } and { "additionalProperties": {} } is proper, but {} which should be interpreted identically was interpreted as a string.

The existence of "additionalPropertis" seems to change output in many other languages.
Elm's and Dart's output from the 2 json schemas seem same, but I'm not sure if that means their outputs are right.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions