Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jeremyfiel opened this issue May 2, 2025 — with Slack · 1 comment
Open

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

jeremyfiel opened this issue May 2, 2025 — with Slack · 1 comment

Comments

Copy link

@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

@gregsdennis
Copy link
Member

This has already been addressed in the upcoming release. We require at least one item in enum.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants