Update json_schemer → 2.0.0 (unknown)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ json_schemer (~> 1.0.3 → ~> 2.0.0) · Repo · Changelog

Release Notes

2.0.0 (from changelog)

For 2.0.0, much of the codebase was rewritten to simplify support for the two new JSON Schema draft versions (2019-09 and 2020-12). The major change is moving each keyword into its own class and organizing them into vocabularies. Output formats and annotations from the new drafts are also supported. The known breaking changes are listed below, but there may be others that haven't been identified.

Breaking Changes

• The default meta schema is now Draft 2020-12. Other meta schemas can be specified using meta_schema.
• Schemas use json-schemer://schema as the default base URI. Relative $id and $ref values are joined to the default base URI and are always absolute. For example, the schema { '$id' => 'foo', '$ref' => 'bar' } uses json-schemer://schema/foo as the base URI and passes json-schemer://schema/bar to the ref resolver. For relative refs, URI#path can be used in the ref resolver to access the relative portion, ie: URI('json-schemer://schema/bar').path => "/bar".
• Property validation hooks (before_property_validation and after_property_validation) run immediately before and after properties validation. Previously, before_property_validation ran before all "object" validations (dependencies, patternProperties, additionalProperties, etc) and after_property_validation was called after them.
• insert_property_defaults now inserts defaults in conditional subschemas when possible (if there's only one default or if there's only one unique default from a valid subtree).
• Error output
  • Special characters in schema_pointer are no longer percent encoded (eg, definitions/foo\"bar instead of /definitions/foo%22bar)
  • Keyword validation order changed so errors may be returned in a different order (eg, items errors before contains).
  • Array dependencies return "type": "dependencies" errors instead of "required" and point to the schema that contains the dependencies keyword.
  • not errors point to the schema that contains the not keyword (instead of the schema defined by the not keyword).
  • Custom keyword errors are now always wrapped in regular error hashes. Returned strings are used to set type:

    >> JSONSchemer.schema({ 'x' => 'y' }, :keywords => { 'x' => proc { false } }).validate({}).to_a
    => [{"data"=>{}, "data_pointer"=>"", "schema"=>{"x"=>"y"}, "schema_pointer"=>"", "root_schema"=>{"x"=>"y"}, "type"=>"x"}]
    >> JSONSchemer.schema({ 'x' => 'y' }, :keywords => { 'x' => proc { 'wrong!' } }).validate({}).to_a
    => [{"data"=>{}, "data_pointer"=>"", "schema"=>{"x"=>"y"}, "schema_pointer"=>"", "root_schema"=>{"x"=>"y"}, "type"=>"wrong!"}]
    

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 27 commits:

• Merge pull request #135 from davishmcclurg/next
• 2.0.0
• Move some special keyword classes to constants
• Add helper for converting enumerators to arrays
• Allow exclusive refs into sibling definitions
• Support schema bundling
• Add classic output format to benchmark
• Test meta schemas match what's published
• Add `Schema#ref` helper
• OpenAPI 3.0
• Update fixtures
• Squashed 'JSON-Schema-Test-Suite/' changes from 7950d9e0..8cdfac41
• Support non-string schema and instance keys
• Add custom `JSONSchemer::Schema#inspect`
• Better error messages
• OpenAPI 3.1
• Lazy load meta schemas
• Short-circuit `valid?` on first keyword error
• Breaking changes
• Update README documentation
• fixmes
• `insert_property_defaults` in conditional schemas
• 100% coverage
• Update fixtures
• Big rewrite
• Merge pull request #134 from davishmcclurg/bundle-exec
• Use `bundle exec` for executable tests

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)