Fix: Resolve escaped "/" and "~" in JSON references #1725
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Oct 6, 2025
This was referenced Oct 16, 2025
This was referenced Oct 24, 2025
This was referenced Nov 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #1573 and #1703
In JSON references, the character "~" and "/" should be escaped as "~0" and "~1", respectively (RFC 6901). The current version of JsonReferenceResolver would fail on resolving these references.
This fix adds support to ref paths containing these special chars by substituting them with "/" and "~" for each reference segment. Note that it replaces "~1" first to avoid transforming "~01" to "/" incorrectly (which should be "~1").