Jon Sequeira

Which version of System.CommandLine are you using?

As far as I'm aware, we don't have another precedent for third-party translations for user-facing strings in a library like what we've enabled in System.CommandLine. We also don't have a...

> That way, the ArgumentResult is created the way it is supposed to be without you needing to try mimicking the behavior of parts of the library itself. I second...

This bug is more general and affects any directive where the name collides with a command defined on the root.

@qmfrederik We really appreciate feedback on the interim builds in the feed that @KalleOlaviNiemitalo pointed to. My only word of caution is that adopting those changes doesn't necessarily mean you'll...

After thinking about this a bit more, I'm not sure the solution proposed in this issue title is the best approach. The core of the problem is that the validation...

We do plan to overhaul the help customization API but it's an open issue as to what that will look like. Broadly speaking, we currently support: * Replacing the entire...

Thanks for the detailed writeup! We're planning to significantly overhaul the `HelpBuilder` API and this is very useful feedback. A couple of quick points not directly related to the `HelpBuilder`...

I see. Another option is to replace the whole options section using `GetLayout` or `CustomizeLayout`. The reason the default is set to `int.MaxWidth` is that there isn't always a console...

You can now set `Option.Arity`. Another thing you can do is to check whether the `ArgumentResult` is implicit (indicating it was created via the default value because there were no...