Skip to content

Clarify how "deprecated" works w/arrays & objects #982

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

Merged
merged 1 commit into from
Sep 25, 2020

Conversation

handrews
Copy link
Contributor

@handrews handrews commented Sep 6, 2020

Fixes #948.

Also updates a missing prefixItems. Fix this by just not being so detailed about special cases and make the general usage more clear, noting that it can produce some odd scenarios.

deprecated, like all annotations, is intended to be handled by applications rather than JSON Schema implementations so there's not a ton of practical impact with this.

@handrews handrews added this to the draft-08-patch1 milestone Sep 6, 2020
@Relequestual Relequestual merged commit 2747ab4 into json-schema-org:master Sep 25, 2020
@handrews handrews deleted the depr branch September 26, 2020 19:37
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

Successfully merging this pull request may close these issues.

rules for 'deprecation' annotation confusing, inconsistent
2 participants