Jon Sequeira
Jon Sequeira
I've opened #1776 to focus the discussion about making the command setup API simpler. I have a prototype that I'll be adding to the issue shortly. Alternative proposals are welcome.
I'm in favor of adding a convention to support specifying culture info. I think this is a really nice idea. Given there's already a convention or two for doing this...
Possibly related: https://github.com/dotnet/runtime/blob/master/docs/design/features/globalization-invariant-mode.md
@KathleenDollard
The current design leaves us with two ways to accomplish the same thing within a command line invocation. For example, to set the culture to "nb-NO", I could do either...
> So if two ways of doing this is an issue, I'd actually rather vote for removing the recognition of environment variables in favor of [culture]. The environment variable approach...
Related: #1125
You can do some of this by exposing the configured `Parser` to your tests and then parsing various command lines and verifying their results directly. Example: https://github.com/dotnet/interactive/blob/97a0651d15d6506bfe0a15dd5e74f8a29568eca4/src/dotnet-interactive.Tests/CommandLine/CommandLineParserTests.cs#L198-L208 And if you...
If you want to get the help output as a string, you can use the `HelpBuilder` directly:
Not currently, but take a look at custom help layouts. These APIs are intended to enable this kind of customization. https://docs.microsoft.com/en-us/dotnet/standard/commandline/customize-help