-
-
Notifications
You must be signed in to change notification settings - Fork 312
Comparing changes
Open a pull request
base repository: json-schema-org/json-schema-spec
base: main
head repository: json-schema-org/json-schema-spec
compare: 2019-09
- 13 commits
- 10 files changed
- 6 contributors
Commits on Apr 8, 2020
-
Merge pull request #883 from jdesrosiers/fix-applicator-schema
Fix applicator meta-schema for unevaluatedProperties
Configuration menu - View commit details
-
Copy full SHA for cc296f0 - Browse repository at this point
Copy the full SHA cc296f0View commit details
Commits on Aug 13, 2020
-
fix output schema check for absoluteKeywordLocation property
it is possible to have both $ref and $recursiveRef in the traversed schema path (cherry picked from commit 36d9fe5)
Configuration menu - View commit details
-
Copy full SHA for 1155fef - Browse repository at this point
Copy the full SHA 1155fefView commit details -
Fix patterns and paths in output schema
Fix a raw "$" in two patterns and add a missing "$defs" in three paths (cherry picked from commit 1b48546)
Configuration menu - View commit details
-
Copy full SHA for d4ea2dd - Browse repository at this point
Copy the full SHA d4ea2ddView commit details -
remove unneeded .* from unanchored patterns
(cherry picked from commit 325e3c4)
Configuration menu - View commit details
-
Copy full SHA for 895e826 - Browse repository at this point
Copy the full SHA 895e826View commit details -
[900] Add missing "type" to applicator meta-schema
(cherry picked from commit 4af51fc)
Configuration menu - View commit details
-
Copy full SHA for e28aeec - Browse repository at this point
Copy the full SHA e28aeecView commit details
Commits on Aug 14, 2020
-
[954] Fix $recursiveAnchor in schema to match spec
The spec allows values of false. This fixes the schema to match the spec. (cherry picked from commit 568e20f)
Configuration menu - View commit details
-
Copy full SHA for 8a6c590 - Browse repository at this point
Copy the full SHA 8a6c590View commit details
Commits on Aug 15, 2020
-
Merge pull request #968 from karenetheridge/2019-09
missing updates to existing 2019-09 metaschemas
Configuration menu - View commit details
-
Copy full SHA for 03fe369 - Browse repository at this point
Copy the full SHA 03fe369View commit details
Commits on Oct 21, 2021
-
Fix 2019-09 hyperschema meta-schemas
The links.json schema uses `$recursiveRef` wrong. In fact, `$recursiveRef` is not capable of expressing the relationship that was intended. With this version, schemas in the `links` keyword are pinned to the 2019-09 hyperschema dialect even if `$recursiveRef` is used to extend the 2019-09 hyperschema dialect. While not exactly what was intended, this covers all but advanced use-cases.
Configuration menu - View commit details
-
Copy full SHA for f25113a - Browse repository at this point
Copy the full SHA f25113aView commit details
Commits on Nov 9, 2021
-
Configuration menu - View commit details
-
Copy full SHA for 41014ea - Browse repository at this point
Copy the full SHA 41014eaView commit details
Commits on Nov 1, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 81e6abb - Browse repository at this point
Copy the full SHA 81e6abbView commit details
Commits on Nov 3, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 0aa7f3d - Browse repository at this point
Copy the full SHA 0aa7f3dView commit details
Commits on Nov 6, 2023
-
Merge pull request #1461 from json-schema-org/gregsdennis/remove-$voc…
…abulary-from-vocabs-2019-09 remove `$vocabulary` from vocab meta-schemas (2019-09)
Configuration menu - View commit details
-
Copy full SHA for aaedf92 - Browse repository at this point
Copy the full SHA aaedf92View commit details
Commits on Jan 8, 2024
-
Merge pull request #1465 from json-schema-org/update-website-links-20…
…19-09 Update the link to the JSON Schema website for 2019-09
Configuration menu - View commit details
-
Copy full SHA for c8eb3d3 - Browse repository at this point
Copy the full SHA c8eb3d3View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...2019-09