Conversation
Implements RFC 7799 for path normalization.
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
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.
Which issue does this PR close?
Implements RFC 7799's path normalization part.
Also closes #6577
Rationale for this change
What changes are included in this PR?
.trim()fromnormalize_pathto preserve whitespace in path components, aligning with POSIX, URI, and object-store conventions where whitespace is significant content..segment filtering to bothnormalize_pathandnormalize_rootso that./a/./bnormalizes toa/b.build_absolute_path,build_rooted_absolute_path, andbuild_relative_pathas the canonical names; deprecate the oldbuild_abs_path,build_rooted_abs_path,build_rel_pathaliases.Are there any user-facing changes?
No
AI Usage Statement
GPT-5.5 with codex implements some code.