Repository navigation
paths: strip C:\\ down to the drive root in without_trailing_slash_windows_path #39228
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
robobun
wants to merge
4
commits into
main
Choose a base branch
from
farm/b1dde18b/without-trailing-slash-drive-root
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.
+183
−3
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
78351de
paths: strip extra separators after a drive root in without_trailing_…
robobun 3213fa9
test: import() of a drive root with extra separators, and correct the…
robobun 37a86a2
Trim doc comments
robobun b713085
Shorten the two remaining multi-line doc comments
robobun 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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,68 @@ | ||
| // `without_trailing_slash_windows_path` (src/paths/string_paths.rs) produces | ||
| // the resolver's directory cache keys: no trailing separator, except that a | ||
| // drive root keeps its one separator (`C:\`), see | ||
| // `Resolver::assert_valid_cache_key`. Its drive-letter arm only runs on | ||
| // Windows hosts, and the only thing that observes its result there is that | ||
| // assertion (debug and ASAN builds; see "directory cache key computation at | ||
| // the drive root" in test/js/bun/resolve/resolve.test.ts), so the arm is bound | ||
| // directly through `bun:internal-for-testing` and its results pinned here on | ||
| // every platform. The same table runs under `cargo test -p bun_paths`. | ||
| // | ||
| // It used to stop stripping one byte past `windows_filesystem_root`, so `C:\\` | ||
| // (the root plus one more separator) came back unchanged and failed the | ||
| // assertion. | ||
| // | ||
| // Namespace import: on a build without the binding, `pathsInternals` is | ||
| // undefined and each test below fails, instead of the file failing to link. | ||
| import * as internals from "bun:internal-for-testing"; | ||
| import { describe, expect, test } from "bun:test"; | ||
|
|
||
| function withoutTrailingSlashWindows(path: string): string { | ||
| return internals.pathsInternals.withoutTrailingSlashWindows(path); | ||
| } | ||
|
|
||
| describe("without_trailing_slash_windows_path", () => { | ||
| test.each([ | ||
| ["C:\\", "C:\\"], | ||
| ["C:/", "C:/"], | ||
| ["c:\\", "c:\\"], | ||
| ["C:\\\\", "C:\\"], | ||
| ["C://", "C:/"], | ||
| ["C:\\/", "C:\\"], | ||
| ["C:\\\\\\\\", "C:\\"], | ||
| ])("%s is the drive root %s", (input, expected) => { | ||
| expect(withoutTrailingSlashWindows(input)).toBe(expected); | ||
| }); | ||
|
|
||
| test.each([ | ||
| ["C:\\foo\\", "C:\\foo"], | ||
| ["C:\\foo\\\\", "C:\\foo"], | ||
| ["C:/foo/", "C:/foo"], | ||
| ["C:\\foo/\\", "C:\\foo"], | ||
| ["C:\\a\\", "C:\\a"], | ||
| ["C:\\foo", "C:\\foo"], | ||
| // Only trailing separators are stripped. | ||
| ["C:\\\\foo\\", "C:\\\\foo"], | ||
| // Drive-relative: `C:` is the root. | ||
| ["C:foo\\", "C:foo"], | ||
| ["C:foo", "C:foo"], | ||
| ])("%s below a drive root becomes %s", (input, expected) => { | ||
| expect(withoutTrailingSlashWindows(input)).toBe(expected); | ||
| }); | ||
|
|
||
| test.each([ | ||
| ["\\\\server\\share\\dir\\", "\\\\server\\share\\dir"], | ||
| // UNC roots are keyed without the separator. | ||
| ["\\\\server\\share\\", "\\\\server\\share"], | ||
| ["\\dir\\", "\\dir"], | ||
| ["dir\\", "dir"], | ||
| ["dir/", "dir"], | ||
| ["\\", "\\"], | ||
| ["/", "/"], | ||
| ["//", "/"], | ||
| ["C:", "C:"], | ||
| ["", ""], | ||
| ])("%s without a drive letter becomes %s", (input, expected) => { | ||
| expect(withoutTrailingSlashWindows(input)).toBe(expected); | ||
| }); | ||
| }); | ||
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.
Uh oh!
There was an error while loading. Please reload this page.