Skip to content

Some inconsistencies in output schema #949

Closed
@stan-sb

Description

@stan-sb

https://github.com/json-schema-org/json-schema-spec/blob/master/output/schema.json
https://json-schema.org/draft/2019-09/json-schema-core.html#rfc.section.10

  1. "basic", "detailed" and "verbose" are defined exactly the same, which means, if output is valid for one of them, it is valid for all of them. This means that, unless the output format is flag, the "oneOf" validation would always fail.

-- Output schema requires "errors" key in case "valid" is false;
-- "errors" is recursively defined as array of "outputUnit"
-- "valid" is required
This means the only way to terminate recursion in case of "valid": false is to include "errors": [], which is misleading.
On the other hand, the output examples sometimes contain "error" key and not "errors". Although not strictly necessary, it'd be good to have "error" defined in the schema.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Closed

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions