Handle other special path prefixes on Windows
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 830
- Forks
- 108
- Avg merge
- 6d 33m
- Merged PRs (30d)
- 2
Description
This is follow-up for #32.
The Rust std library recently got better support for handling special Windows paths in https://github.com/rust-lang/rust/pull/89174 (stabilized in 1.58.0).
While going through the PR, I noticed some other path prefixes that I was not aware of: https://github.com/rust-lang/rust/pull/89174/files#diff-1d1bc84d05775ebd4b147542747b8e57edf520a54935771ce1d85f383596aa64R169-R174
And digging even further, I have seen some sources claim that way Windows handles paths is incredibly complex: https://googleprojectzero.blogspot.com/2016/02/the-definitive-guide-on-win32-to-nt.html (All I can really say is that the 36-year lineage of Windows did not do it any favors.)
Contributor guide
No contributing guide indexed for this repository
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 by reviewing issue #32 and the Rust std PR #89174, including the referenced Windows path-prefix changes. Identify which additional special prefixes rfd should handle and define completion as support for those prefixes in the file dialog without regressing existing Windows path handling.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- desktop, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100