sillsdev / sillsdev/overcrowdin
Normalize paths specified on the command line
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Files specified using the command line option -f, -file can have paths that are absolute or relative, or that contain arbitrary directory separator characters. These paths are presently used as keys without any modification or vetting. It would be nice if they were somehow normalized. Some options:
- remove any Windows drive letters (e.g.
C:) and normalize to Unix directory separators - use only the filename as the key (this may require less code to enforce, but also gives users less flexibility)
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 tracing command-line handling for the -f, -file option through to where the supplied path becomes a key. Before changing code, resolve whether drive letters and separators should be normalized or whether only filenames should be used; done means the chosen behavior is consistently applied to absolute, relative, and mixed-separator paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100