-
Notifications
You must be signed in to change notification settings - Fork 280
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
The schema location is not always computed correctly for ReferenceSchema #233
Comments
Another problem is that if the referred definition is in the same file, the reference schema has the location null, and the referred schema has the location of the referred definition. See the test case below.
|
* wiring SchemaLocation into SchemaBuilder * adding `JSONPointer#getRefTokens()` * tracking the location in both `Schema#location` and `Schema#schemaLocation` (unfortunately the latter is protected so needs to be maintained) * adding `SchemaLocation#parseURI()` and using it in `ReferenceLookup`
Hello @octavianN , thank you for reporting it. It is now fixed on current |
Hello,
Please note that the schema location for the "city" schema is "#/properties/billing_address/properties/city". But this location does not exists.
Maybe the location should be something like this: "#definitions.json/definitions/address/properties/city".
The text was updated successfully, but these errors were encountered: