Sub-commands? about oakton

[cocowalla]

For reference, I worked around this by handling the top level commands myself, then building a CommandExecutor for the specified command: Gist

@jeremydmiller BTW, I really like how simple yet well-featured this library is compared to the bigger ones!

[jeremydmiller]

You can use arguments to effect sub commands. Your Oakton command can vary on what it actually does by just doing a switch in the Execute on the argument. Oakton was originally built in the FubuCore days -- for better or worse -- as a way to build tools like the git cli

[cocowalla]

Do you mean using something like this:

[Description("Work with volumes", Name = "volume")]
public class VolumeCommand : OaktonAsyncCommand<VolumeInput>
{
	private readonly AppConfig appConfig;

	public VolumeCommand(AppConfig appConfig)
	{
		this.appConfig = appConfig;

		Usage("Work with a volume").Arguments(x => x.Action, x => x.Name);
	}

	public override async Task<bool> Execute(VolumeInput input)
	{
		// Switch on input.Action here
	}
}

public class VolumeInput
{
    public CommandAction Action { get; set; } = VolumeAction.ls;
    public string Name { get; set; };

    public enum CommandAction
    {
        create,
        ls,
        inspect,
        rm,
    }
}

Let's say I also wanted a command my-app volume ls, i.e. the ls action, but without any arguments - any idea how I could achieve this while still keeping the CommandUsage from the above code working?