Using a private API in jsonschema that has now been removed
See original GitHub issuecore/jsonutils/renamer.py
uses the jsonschema.compat
API which is a private API.
The new 4.0.0 and 4.0.1 versions of jsonschema
removes that API.
ref: https://github.com/Julian/jsonschema/issues/843#issuecomment-931247200
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Raise JSON Schema Validation Error when key does not exist ...
Validation errors raise correctly for keys that have been defined when provided the wrong type, but if I add a random key to...
Read more >Understanding JSON Schema
JSON Schema is a powerful tool for validating the structure of JSON data. However, learning to use it by reading its.
Read more >OpenAPI v3.1 and JSON Schema | APIs You Won't Hate
OpenAPI Schema is a vocabulary of JSON Schema 2020-12; type arrays are now supported; nullable has been removed; arbitrary keywords are now ......
Read more >JSON:API — Frequently Asked Questions
Now that JSON:API has reached a stable version 1.0, it will always be backwards compatible using a never remove, only add strategy. A...
Read more >How to validate JSON Schema - YouTube
REST Assured Beginner Tutorial 10 | How to validate JSON Schema ... Please share this knowledge with everyone If my work has helped...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
As a temporary workaround, if anybody encounters this issue, you can ‘downgrade’ your
jsonschema
version withI just ran into this issue (the
cfn
command fails sayingjsonschema.compat
has not been found).I can confirm @richardhboyd’s workaround did make the problem go away for me, but this should definitely be fixed upstream.