We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
Related to #7980, I checked for more attributes where I had made the mistake of introducing a <container>[str] annotation which should read <container>[str | int]
<container>[str]
<container>[str | int]
I didn't have an example usage in mind, so I tried adding a for x in schema_path: assert isinstance(x, str) to the error init and running jsonschema's tests. It failed (as expected) on ints, so I'm certain that the original annotation I added has an error in it and I'm reasonably confident that str | int is the correct form.
for x in schema_path: assert isinstance(x, str)
str | int
schema_path, relative_schema_path, and absolute_schema_path are all (related) attributes of jsonschema errors which contain str | int but were accidentally annotated as containing str. Fix them for accuracy.
jsonschema
str
Sorry, something went wrong.
Fix jsonschema exception str|int containers
994ba98
schema_path, relative_schema_path, and absolute_schema_path are all (related) attributes of `jsonschema` errors which contain `str | int` but were accidentally annotated as containing `str`. Fix them for accuracy.
According to mypy_primer, this change has no effect on the checked open source code. 🤖🎉
b2aaed1
Successfully merging this pull request may close these issues.