Consider adding and using a proper CLI parser
Open
Nobody has claimed this yet.
C-task
- Dominant language
- Rust
- Stars
- 14.6k
- Forks
- 734
- Avg merge
- 8h 40m
- Merged PRs (30d)
- 4
Description
See: https://github.com/microsoft/edit/pull/143#issuecomment-2897277505
...and following. The benefits are rather obvious including correct -- handling.
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 by reading the discussion in microsoft/edit#143, especially the linked issue comment and following thread, then locate the current command-line argument handling. Define the parser's required behavior, including correct -- handling, and consider the work complete when the CLI consistently parses the documented arguments and tests cover the relevant cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100