Skip to content

v3.2: Strengthen generic data types to a SHOULD #4657

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
wants to merge 1 commit into
base: v3.2-dev
Choose a base branch
from

Conversation

handrews
Copy link
Member

@handrews handrews commented Jun 5, 2025

I thought I had already done this one-word change but I guess I forgot!

This was added as a MAY in 3.1.1 but we can make it a SHOULD in 3.2.

I'd love to make it a MUST but there might be scenarios where it is not feasible, or where alternate interpretations are valid. For example, the OAS schema and the JSON Schema metaschema use $dynamicRef, but to support a recursive data structure rather than a generic one.

This is the minimum change to more strongly encourage support for this much-demanded feature (it closed 5 separate issues when we added it) that currently is one of the least-supported JSON Schema keywords despite high demand.

  • schema changes are included in this pull request
  • schema changes are needed for this pull request but not done yet
  • no schema changes are needed for this pull request

This was added as a MAY in 3.1.1 but we can make it a SHOULD in 3.2.
@handrews handrews added this to the v3.2.0 milestone Jun 5, 2025
@handrews handrews requested review from a team as code owners June 5, 2025 19:07
@ralfhandl ralfhandl requested a review from a team June 6, 2025 10:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants