addSubcommand without name or alias

[andbleo]

CommandLine.addSubcommand requires a string name and optionally an array of aliases. Would it be possible to add a version of addSubcommand that just takes in an Object and reads the name and aliases from the @command annotations? If the subcommands annotation can get the name and alias for subcommands, it seems like the programmatic way of adding subcommand should be able to as well.

[remkop]

Away from PC now, but this sounds reasonable.

I’m thinking to throw an InitializationException when the specified object doesn’t have a @Command annotation, or is missing the name attribute.

Thoughts?

[andbleo]

That makes sense to me.

[remkop]

I'd love to include this in picocli-4.0, but there are a lot of items on the todo list for that release...

Do you think you will be able to provide a pull request with unit tests?

[remkop]

This is now available in master. It tries to get the name from the @Command(name = "...") annotation, otherwise from the first @Command(aliases = {"..", "..."}) alias. Should also work for programmatically constructed CommandSpec and CommandLine objects, without an annotated user object.

If no name is found, an InitializationException is thrown.

Can you verify this works as expected?