Jon Sequeira
Jon Sequeira
It's hard to know what's the right number of overloads. I think there are too many and it makes intellisense a bit confusing. (The source generator approach we've been experimenting...
In beta 4, in order to keep the combinatorial overload explosion to a minimum, we only provide two flavors of `SetHandler`: * Those that bind parameters for you, like this:...
You could define you own if you wanted to take this approach. I don't encourage using exceptions to communicate with the user.
I suppose another option that wouldn't result in an overload explosion is to require returning an exit code on all of the `SetHandler` APIs. It would be a fairly disruptive...
This is something we've been considering, in fact. We'd have immediate use for it in .NET Interactive.
Would you consider submitting a PR?
Can you explain a bit more about what you're trying to do and why this output is your expectation? Also, examples using precise strings without the C# escaping would be...
This is complicated and hard to talk clearly about. 😅 Going back to the previous example and taking System.CommandLine out of the picture for a moment, the following would work...
Could you say a bit more about what you're wanting to do? One hint that might or might not be relevant: If you keep a reference to the `Option` from...
We don't currently have APIs to find ancestors or descendants directly, only parents and children. But it's a simple enough thing to do with a helper method so I'm not...