Skip to content

Commit 6947eb1

Browse files
committed
Note that we may remove "dependencies"
This was discussed in the if/then/else issue. There was significant support for removing "dependencies" as it is more straightforward, although sometimes more verbose, to implement the same funcitonality with if/then/else. Rather than going straight to ripping it out, let's give if/then/else a bit of time to gather feedback. Make a note of it to warn that "dependencies" may be removed, which will hopefully provoke some feedback on that idea as well.
1 parent 4f9bcb0 commit 6947eb1

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

jsonschema-validation.xml

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -597,6 +597,15 @@
597597
</section>
598598

599599
<section title="dependencies">
600+
<t>
601+
<cref>
602+
Now that "if", "then", and "else" are keywords, it is not clear whether
603+
there is any benefit in keeping dependencies. It is frequently
604+
misunderstood and seems to be rarely used. Depending on feedback
605+
with "if", "then", and "else", this keyword may well be removed in a
606+
future draft.
607+
</cref>
608+
</t>
600609
<t>
601610
This keyword specifies rules that are evaluated if the instance is an object and
602611
contains a certain property.

0 commit comments

Comments
 (0)