Suggestion: make this tool System.CommandLine friendly
iSeiryu opened this issue · comments
Microsoft created their own package to build CLI tools:
https://github.com/dotnet/command-line-api
https://learn.microsoft.com/en-us/dotnet/standard/commandline/get-started-tutorial
Would it make sense to build Sharprompt on top of their package?
The CommandLine API has a different purpose to begin with. While it provides the ability to parse command line arguments, Sharprompt provides an interactive UI.
Could this package use their arguments parser/binder instead? They support sub-commands arguments and flags.
It has a completely different purpose than the Commandline API.
Therefore, Sharprompt will not support them, but they can be used at the same time.