Bug fix: relative URI starting with a slash #80
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.
Hi there! Thanks for the work on this library!
I am new to using JSON schemas, so I am not completely familiar with the details of the specs, but some JSON schemas that I am working with lately have had an
$id
field as a relative URI starting with a slash/
with additional slashes (e.g./foods/apple
). In theExonerate.Context.id_swap_with/5
function, theupdated_resource
variable merges theid
(/foods/apple
) with the resource (/foods/apple
) erroneously resulting in/foods/foods/apple
and then crashing when it cannot find/foods/foods/apple
in the ets table.This change updates the extended
URI.merge
function on a relative URL to include expected behavior when thedest_path
starts with a slash/
, which is to completely replace the path with thedest_path
. Example from the standardURI.merge
function:I would like to add a unit test for this change as well, but I could use some help if possible.
Thanks again, and let me know how I can help.