commandlineparser / commandlineparser/commandline
OptionsBase class for all cmd line projects in a solution
- Dominant language
- C#
- Stars
- 4.8k
- Forks
- 478
- PR merge metrics
- No merged PRs in 30d
Description
The old version allowed us to create an OptionsBase class. Most of it was easily migrated to the new lib API, but I'm not sure how to tackle the Usage/Help option because the ApplicationAlias property of the Usage attribute cannot be dynamically set, and I see no way to replace this snippet from the OptionsBase:
```
string fileName = System.Diagnostics.Process.GetCurrentProcess().MainModule.FileName;
help.AddPreOptionsLine(string.Format("Usage: {0}.exe [/i c:\\aossrvtest.ini] [/d 10]", fileName));
help.AddPreOptionsLine(" ");
help.AddPreOptionsLine(" ");
help.AddPreOptionsLine("Arguments:");
help.AddOptions(this);
```
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by comparing the old OptionsBase implementation with the new lib API, focusing on the Usage attribute, its ApplicationAlias property, and the Help-generation snippet shown here. Determine whether the new API can support executable-specific usage text and argument listing for all command-line projects in a solution; done means a documented replacement approach is identified and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100