Open PonchoPowers opened 1 month ago
While i am not associated nor involved with the S:CL project, i very much doubt that such would be within the scope of what the S:CL maintainers try to achieve. What you are looking for is in my opinion a typical example of where its up to the (wider) .NET community to create, maintain and share such packages (regardless of which particular commandline parser being used).
Thanks, I figured as much, but wanted to throw it out there in the hope that someone starts a project as such. If this gets little interest I might start one myself.
It would be nice to have a library of CliCommands that are maintained as a project within itself so that each developer doesn't have to come a long and write up all the boilerplate code each time they want to parse a command line.
A bit like types for TypeScript, the cli commands would then be used to parse commands for well-known command line tools such as Node.js.
Node.js has a comprehensive set of options, and to fully parse a Node.js command would take a mammoth amount of work, but it isn't just Node.js, there are many other libraries where it would take a long time to write all the code required to properly understand the command.
I am not proposing we do this as part of the command-line-api project, I am proposing another project that can be used alongside this that will provide some useful definitions for developers.