-
-
Notifications
You must be signed in to change notification settings - Fork 313
Why doesn't the applicator meta-schema define "type"? #900
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
Comments
Which one? Looks present here |
Oops. I don't know why I put "validation". I meant "applicator". |
@ssilverman it was either an accident, or I decided that I wanted the vocabulary schemas to constrain the keywords but not the overall type (deferring that to the dialect meta-schema, meaning the schemas that are not under |
Given the other schemas in |
This update needs to be also made for the 2019-09 schemas, and then released to the website. |
PR created in #968. |
@Relequestual I’m confused. This is already a 2019-09 schema? What else needs to change? |
Ok, I've sorted this out. It's a different branch. |
This is now resolved. |
I believe this issue can be closed. |
It seems like
"type": ["object", "boolean"]
is missing.The text was updated successfully, but these errors were encountered: