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.

Sign up for GitHub

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
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions jsonschema-validation.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1083,7 +1083,7 @@
"contentSchema": {
"type": "array",
"minItems": 2,
"items": [
"prefixItems": [
{
"const": {
"typ": "JWT",
Expand Down Expand Up @@ -1177,10 +1177,10 @@
the entire resource being described MAY be removed in the future.
</t>
<t>
When the "deprecated" keyword is applied to an item in an array by means of
"items", if "items" is a single schema, the deprecation relates to the whole
array, while if "items" is an array of schemas, the deprecation relates to
the corresponding item according to the subschemas position.
The "deprecated" keyword applies to each instance location to which the
schema object containing the keyword successfully applies. This can
result in scenarios where every array item or object property
is deprecated even though the containing array or object is not.
</t>
<t>
Omitting this keyword has the same behavior as a value of false.
Expand Down