Use default base URI for exclusive refs #147
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In drafts 7 and earlier, all keywords except
definitions
are ignored when$ref
is present. This includes$id
, which means refs are resolved using the schema's inherited base URI (default or parent). Currently, when$id
is present, the inherited base URI isn't being registered as a ref resolution resource (withID_KEYWORD_CLASS.new
), which causes JSON pointer ref resolution to fail. The fix here is to add the exclusive ref case for theID_KEYWORD_CLASS.new
call.The rest of the changes are from if/else cleanup.
Closes: #146