Skip to content

Commit 8be576a

Browse files
committed
Clarify dependencies deprecation
It is focused on the subschema form, not the string array form.
1 parent 393ff78 commit 8be576a

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

jsonschema-validation.xml

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -608,10 +608,13 @@
608608
<t>
609609
<cref>
610610
Now that "if", "then", and "else" are keywords, it is not clear whether
611-
there is any benefit in keeping dependencies. It is frequently
612-
misunderstood and seems to be rarely used. Depending on feedback
613-
with "if", "then", and "else", this keyword may well be removed in a
614-
future draft.
611+
there is any benefit in keeping the schem form of dependencies. It is
612+
frequently misunderstood, and having a form that takes a subschema
613+
as well as a form that takes a primitive value is particularly
614+
confusing. And it seems to be rarely used. Depending on feedback
615+
with "if", "then", and "else", the schema form of this keyword may
616+
well be removed in a future draft. Current thought is that the string
617+
form (giving property names in an array) is a useful shortcut.
615618
</cref>
616619
</t>
617620
<t>

0 commit comments

Comments
 (0)