-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support $refs with implicit url base #5
Comments
Hmm, actually the problem seems to be that |
Thanks for the report and apologies for the delay investigating. There's been a problem with the scheme 'urn'. It seems it doesn't play nice with the constructor for java.net.URI, which I use throughout. I pushed enough to fix the precise issue above (thanks for the test case) but will need to do more digging to make sure it works throughout. |
When I use |
Sorry to read that; could you confirm that you are using 0.11.2. If you are, could you paste an example of a failed case here? You can check it in advance on https://tryjsonschematypes.appspot.com/#validate |
I got for {
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "urn:java:common.proto.Message",
"title": "Message itself",
"type": "object",
"properties": {
"head": {
"type": "object"
},
"body": {
"$dynamicRef": "#body"
}
},
"required": ["head", "body"],
"additionalProperties": false,
"$defs": {
"body": {
"$dynamicAnchor": "body",
"type": "object"
}
}
} |
When loading the following schema I get a warning:
The text was updated successfully, but these errors were encountered: