docs: clarify %2f encoding requirement for scoped package paths#37
Open
docs: clarify %2f encoding requirement for scoped package paths#37
Conversation
Scoped packages must encode the scope separator as %2f in the URL path. A literal slash is treated as two path segments and will not resolve. Registry implementations must preserve %2f without decoding it to / before routing. I'm not advocating for that solution, my goal is to document it for API compatiblity.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Scoped packages must encode the scope separator as
%2fin the URL path. A literal slash is treated as two path segments and will not resolve. Registry implementations must preserve %2f without decoding it to / before routing.I'm not advocating for that solution, my goal is to document it for API compatibility.
References
Similar concerns were brought up on #9 but not documented for registry API.