PowerShell / PowerShell/vscode-powershell
File operations won't work on case-sensitive file systems on macOS
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description
The normalizeFilePath function we use in some file manipulation functions assumes that all macOS file systems are case-insensitive, which is not true.
HFS+ and APFS have case-sensitive variants that we should try not to break. Also worth noting that NTFS is also case-sensitive, but Windows is not.
In general, I think we should not try to second guess the operating system and be case-preserving.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with normalizeFilePath in src/features/ExtensionCommands.ts around the linked line, then trace the file-manipulation functions that use it. Check how the current behavior treats path casing on macOS and verify that the completed change preserves casing rather than assuming the operating system is case-insensitive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, typescript, vscode
- Domain
- devtools, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100