Skip to content

missing updates to existing 2019-09 metaschemas #968

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

Merged
merged 5 commits into from
Aug 15, 2020

Conversation

karenetheridge
Copy link
Member

These schema fixes have been made in master and not yet applied to the 2019-09 branch.

karenetheridge and others added 4 commits August 13, 2020 10:27
it is possible to have both $ref and $recursiveRef in the traversed schema path

(cherry picked from commit 36d9fe5)
Fix a raw "$" in two patterns and add a missing "$defs" in three paths

(cherry picked from commit 1b48546)
@ssilverman
Copy link
Member

ssilverman commented Aug 14, 2020

I suppose this has to wait for PR #945. Just a reminder to @Relequestual to get that in first so we can cherry-pick that PR into this one. (Closes #900 too.)

The spec allows values of false. This fixes the schema to match the spec.

(cherry picked from commit 568e20f)
@Relequestual
Copy link
Member

Previous merged PRs:
#940
#923
#963
#945

As such, I shan't delay merging this and updating on the website.

@Relequestual Relequestual linked an issue Aug 15, 2020 that may be closed by this pull request
@Relequestual Relequestual merged commit 03fe369 into json-schema-org:2019-09 Aug 15, 2020
Relequestual added a commit to Relequestual/json-schema-org.github.io that referenced this pull request Aug 15, 2020
@karenetheridge karenetheridge deleted the 2019-09 branch August 15, 2020 16:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Why doesn't the applicator meta-schema define "type"?
3 participants