Jon Sequeira

Here's a list of proposed changes, intended to move some of the most common types into the root `System.CommandLine` namespace while leaving other less commonly-used types in their more specific...

My first impression here is that this might be a different type from either `string` or `FileInfo`, and perhaps be a new option type we include in the library. Would...

> Another suggestion, although more work, is to incorporate the process of defaulting to environment variables into the library itself. This is a common enough need that it might be...

We've been making a number of changes to make help easier to customize. One approach that can work here is the following. Caveats afterward. ```cs using System.CommandLine; using System.CommandLine.Builder; using...

You can override the default help output using the APIs described here: https://docs.microsoft.com/en-us/dotnet/standard/commandline/customize-help#customize-help-for-a-single-option-or-argument. Take a look at specifying a different `secondColumnText` and let us know whether this works for you.

We've been discussing doing something like this as part of making completions work without users needing to install `dotnet-suggest` and shim shell scripts manually.

If the problem you're trying to solve is specific to dependency injection, another option is the one described here: https://github.com/dotnet/command-line-api/issues/1750#issuecomment-1152707726 Any thoughts on this approach?

`Bind.FromServiceProvider()` and `Bind.FromServiceProvider()` should work.

> Basically, the following code compiles, but fails at runtime for me: @craignicol You'll need to pass the symbols you want to bind to `SetHandler`.

We're going to improve this error message. This API should also be much easier than the old one to add analyzer support for.