-
-
Notifications
You must be signed in to change notification settings - Fork 583
New issue
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
BUG: validator tries to resolve $id although there are no outside references #1012
Comments
Workaround:
That workaround looks problematic to me because |
It looks like the issue lies in
which strips the |
Hello there! This, along with many many other The next release of It looks from my testing like indeed this specific example works there! If you still care to, I'd love it if you tried out the beta once it is released, or certainly it'd be hugely helpful to immediately install the branch containing this work (https://github.com/python-jsonschema/jsonschema/tree/referencing) and confirm. You can in the interim find documentation for the change in a preview page here. I'm going to close this given it indeed seems like it is addressed by #1049, but feel free to follow up with any comments. Sorry for the delay in getting to these, but hopefully this new release will bring lots of benefit! |
This issue does indeed appear solved in However, the new version throws new |
The ref resolution regression is discussed in another issue: #1089 |
Looking at the following MCVE:
This raises:
Full Traceback
According to my reading of the spec, this should validate just fine. Hyperjump also finds these JSONs valid (after removing the
# comment line
).However,
jsonschema
fails here. It looks like two things are needed for the error to happen:"$id"
field wherejsonschema
doesn't know the scheme (or a string that looks like a URI)."$ref"
statements.According to the spec:
jsonschema
validates the file just fine if the"$id"
doesn't contain a colon. I don't even understand why it tries to resolve the"$id"
.Related: #313
The text was updated successfully, but these errors were encountered: