Skip to content

Commit 64ca2b9

Browse files
committed
Clarify how "deprecated" works w/arrays & objects
1 parent 3f1b1c4 commit 64ca2b9

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

jsonschema-validation.xml

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1083,7 +1083,7 @@
10831083
"contentSchema": {
10841084
"type": "array",
10851085
"minItems": 2,
1086-
"items": [
1086+
"prefixItems": [
10871087
{
10881088
"const": {
10891089
"typ": "JWT",
@@ -1177,10 +1177,10 @@
11771177
the entire resource being described MAY be removed in the future.
11781178
</t>
11791179
<t>
1180-
When the "deprecated" keyword is applied to an item in an array by means of
1181-
"items", if "items" is a single schema, the deprecation relates to the whole
1182-
array, while if "items" is an array of schemas, the deprecation relates to
1183-
the corresponding item according to the subschemas position.
1180+
The "deprecated" keyword applies to each instance location to which the
1181+
schema object containing the keyword successfully applies. This can
1182+
result in scenarios where every array item or object property
1183+
is deprecated even though the containing array or object is not.
11841184
</t>
11851185
<t>
11861186
Omitting this keyword has the same behavior as a value of false.

0 commit comments

Comments
 (0)