Jon Sequeira
Jon Sequeira
It's an unintended behavior so I think it probably makes sense to make it consistent now instead of maintaining it forever.
There's a separate issue to improve filename completions (#1697). We'd like System.CommandLine to do a better job at filename completions rather than the current all-or-nothing approach where you get either...
Could you expand on the example? What was the code you were using before and what do you need to do now?
This is a great suggestion. We're not too concerned about breaking changes since we're still in beta, but this would also make it easier for people to do the right...
You'll need to have access to your `Option` instance that was used as a global option and pass it into `SetHandler`.
The option is global within the command line interface. Effectively, `AddGlobalOption` lets you replace calls like this: ```csharp var option = new Option("-x"); var rootCommand = new RootCommand { option,...
Thanks, @abbotdev. Your example seems to mix instantiating subcommands within your constructors while passing in the global option. I wonder if a static property on a base class would be...
Can you provide a code sample to reproduce this?
I'm not seeing this issue when calling `Invoke` on the `Parser` returned from `CommandLineBuilder.Build`. I do see it when I call `Invoke` directly on the `RootCommand`. That should allow people...
You can always take in an `InvocationContext` in your handler and set `InvocationContext.ExitCode`.