Use System.CommandLine for CLI parsing #888
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been using S.CL a lot on the .NET SDK, and while it's not quite as feature-ful as Argu it is way faster, and our use of Argu isn't super complex anyway.
S.CL also encourages a layering of options such that I can put together some middleware to take care of different slices of the startup code (like logging configuration) and get it out of the way of the main app startup code.
Anyway, seems to be working locally. Help output for the CLI looks good:
One thing that's useful is testing the parsing of your CLI app, which you can do with the
[parse]
directive. This lets you see how the command would be parsed so you can make sure that nothing erroneous happensHere, the command
fsautocomplete
is given the option--filter
, and that option has 4 arguments. This is nicer (and more capable!) parsing code than we had for filters before IMO.