Jon Sequeira
Jon Sequeira
There are unaddressed comments and merge conflicts that need to be resolved.
@wli3 Any ideas on this one?
The current workaround for this is to set `RootCommand.Name` to the desired name.
It looks like CommandLineUtils requires a similar workaround, which is to reiterate the tool name in the C# code. From the sample (comment mine): ```cs namespace SampleCLI { [Command(Name =...
We plan to continue to support netstandard2.0. Source generator support will be at another layer.
A name change is likely here as the single-word type name is more prone to collide with type names in other namespaces.
> See the GetIssuedCommand method? It was my way to get the command. @JobaDiniz You should be able to get this information using `ParseResult.CommandResult.Command.Name`. To see the actual tokens that...
@tmds We're putting off GA until after we've settled #1891 and any additional issues that come out of that work. I'll add the issues within #1891 (since it's a meta-issue)...
> Please consider giving it a name. We could refer to the "web stuff" in .NET, but we don't because it's so massive and deserved a name, viz. "ASP.NET", similarly,...
> Particularly --option=argument, where the option was not designed to take an argument (https://github.com/dotnet/command-line-api/issues/2010), is parsed the same as --option argument against existing practice in getopt_long and argp_parse. This looks...