How do I set an Action in the Command constructor when SetAction() uses internal AnonymousSynchronousCommandLineAction()?

[ptr727]

I am trying to remove usage of NamingConventionBinder and I am binding directly to options, but I'm having difficulty constructing commands using the constructor initializer only.

Calling SetAction() that uses an internal only class AnonymousSynchronousCommandLineAction to set the CommandLineAction member:

        Command test = new("defaultsettings")
        {
            Description = "Create JSON configuration file using default settings",
            Options = { _settingsFileOption },
        };
        test.SetAction(_ => Program.DefaultSettingsCommand());

But I want to use constructor initialization only, is there a simpler way to do this vs. having to create my own copy of AnonymousSynchronousCommandLineAction?

        rootCommand.Subcommands.Add(
            new("defaultsettings")
            {
                Description = "Create JSON configuration file using default settings",
                Action = new AnonymousSynchronousCommandLineAction(_ => // <<-- does not compile as it is declared internal
                    Program.DefaultSettingsCommand()
                ),
                Options = { _settingsFileOption },
            }
        );

Seems like I'm just missing something?

[jonsequitur]

You can create your own type derived from either SynchronousCommandLineAction or AsynchronousCommandLineAction.

[baronfel]

Here's a concrete example from the .NET CLI: dotnet/sdk#49664

[ptr727]

That's basically what I ended up doing:

    private class CommandHandler(Func<ParseResult, int> action) : SynchronousCommandLineAction
    {
        public override int Invoke(ParseResult parseResult) => action(parseResult);
    }

        rootCommand.Subcommands.Add(
            new("defaultsettings")
            {
                Description = "Create JSON configuration file using default settings",
                Action = new CommandHandler(_ => Program.DefaultSettingsCommand()),
                Options = { _settingsFileOption },
            }
        );

It just seems like such a common thing that everybody that uses an initialization pattern will need to do, why not just support it out of the box, e.g. make the AnonymousxxxCommandLineAction classes public, or provide a slimmer variant that is public, or allow direct lambda assignemnt to Action?