-
Notifications
You must be signed in to change notification settings - Fork 4
Remove leading slash from file name if path is absolute #53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
zxvfc
wants to merge
13
commits into
uutils:main
Choose a base branch
from
zxvfc:remove_leading_slash_when_creating_archive
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
0aa2f0d
Remove leading slash from file name if path is absolute
zxvfc 7ec4f19
Refactor path's name normalization
zxvfc 24e5c99
Strip leadin '/' for folders too
zxvfc 4aba913
Merge branch 'main' into remove_leading_slash_when_creating_archive
zxvfc f4a36fb
Fix fromatting after merge
zxvfc 45b3fd8
Add test for archive creation with absolute path
zxvfc 179ed6a
Fix tests for windows
zxvfc 40d9b32
Fix path normalization for windows
zxvfc d902eee
Fix tests for windows
zxvfc fcf3d1d
Improve naming of tests
zxvfc bddcd5b
Split test for create and extract from absolute path
zxvfc 80fe0e8
Fix style
zxvfc 2abf164
Fix style
zxvfc File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Some comments aren't visible on the classic Files Changed page.
There are no files selected for viewing
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 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we have it in uucore, please use it:
https://docs.rs/uucore/latest/uucore/fs/fn.normalize_path.html
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, good to know!
But I think
uucode::fs::normalize_pathdo a different job. It is doing a normalization of path (dir/foo/../file->dir/file) while my function is stripping leading/orC:prefix. I guess it will be more correct to just rename my function to something liketo_relative_pathordrop_root_prefixto avoid confusion.But anyway, I guess, it also requires a normalization, since path in archive shouldn't contain
../. Shall I do it in this PR or better to keep it separate?