-
-
Notifications
You must be signed in to change notification settings - Fork 307
Add contains
keyword
#32
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.
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
Labels
Comments
@BigBlueHat , @awwright : I just realized I re-filed this as issue #63 as I did not think anyone had migrated it over. Since I copied the full text of the proposal in that issue, can I request that we close this one and keep #63 ? Or I could copy stuff over here. |
handrews
added a commit
to handrews/json-schema-spec
that referenced
this issue
Oct 28, 2016
This addresses the enhancement requested in issues json-schema-org#32 and json-schema-org#63. Only the single-schema form from json-schema-org#63 is added here as the multi-schema form did not gather significant support in the absence of a clear use case.
Done! Please close unless we missed something (I don't have the permissions to close this). |
Closed as merged. |
This was referenced Jul 10, 2020
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just surfacing this proposal from https://github.com/json-schema/json-schema/wiki/contains-%28v5-proposal%29
It would greatly simplify JSON Schemas such as this one:
https://github.com/w3c/web-annotation-tests/blob/master/common/contextValue.json#L15-L26
It has been implemented in ajv.
/cc @awwright @epoberezkin
The text was updated successfully, but these errors were encountered: