Migrate from JsonSchema 3 to JsonSchema 4 (#160) #165
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* feat: migrated jsonschema.RefResolver to referencing.Registry * fixed typo in changie output for PR 160 * corrected whitespace for pre-commit linter * corrected linter violations * removed subscript from Resource * clean up linter violation for Tuple
3 tasks
tlento
approved these changes
Oct 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #135
Description
We're backporting jsonschema 4 to unblock people migrating from dbt-core 1.5 to 1.6. Most packages require jsonschema 4.x, something like 90% of people are using jsonschema 4.x, not migrating to it is actively blocking people.
Checklist
changie newto create a changelog entry