Skip to content

enum keyword was relaxed in draft5, metaschemas not updated #1601

Open
@jeremyfiel

Description

@jeremyfiel

@jviotti also pointed out the metaschemas diverge on this change.

> Actually it's a bit more subtle. While the spec indeed says SHOULD in some cases, the meta-schemas often still enforce this:
> • Draft 4: https://json-schema.org/draft-04/schema#. It has minItems: 1
> • Draft 6: https://json-schema.org/draft-06/schema#. It has minItems: 1
> • Draft 7: https://json-schema.org/draft-07/schema#. It has minItems: 1
> • 2019-09: https://json-schema.org/draft/2019-09/meta/validation. Allows any number of items
> • 2020-12: https://json-schema.org/draft/2020-12/meta/validation. Allows any number of items
>

Slack Message

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions