Skip to content
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

Jump to bottom

Clarify dependencies deprecation #444

Merged
merged 1 commit into from
Oct 18, 2017
Merged

Clarify dependencies deprecation #444

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
11 changes: 7 additions & 4 deletions jsonschema-validation.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -608,10 +608,13 @@
<t>
<cref>
Now that "if", "then", and "else" are keywords, it is not clear whether
there is any benefit in keeping dependencies. It is frequently
misunderstood and seems to be rarely used. Depending on feedback
with "if", "then", and "else", this keyword may well be removed in a
future draft.
there is any benefit in keeping the schema form of "dependencies".
It is frequently misunderstood, and having a form that takes a subschema
as well as a form that takes a primitive value is particularly
confusing. And it seems to be rarely used. Depending on feedback
with "if", "then", and "else", the schema form of this keyword may
well be removed in a future draft. Current thought is that the string
form (giving property names in an array) is a useful shortcut.
</cref>
</t>
<t>
Expand Down