Mixing Required + Non-Required Options in an ArgGroup -- required options not validated

I have a use case similar to other issues – options with sub-options. For example: cli --group=alpha --opt1=1 --group=bravo --opt2=foo

I’m trying something like this:

class Group {
    @Option(names = {"--group"}, required = true) String name;
    @Option(names = {"--opt1"}) int opt1;
    @Option(names = {"--opt2"}) String opt2;
}

@ArgGroup(exclusive = false, multiplicity = "0..*") List<Group> groups;

This almost works:

• cli --group=alpha --opt1=1 --group=bravo --opt2=foo results in groups = [{name=alpha, opt1=1}, {name=bravo, opt2=foo}]
• cli --opt1=1 --group=alpha --opt2=foo (weird that --opt1 comes before --group, but allowed) results in groups = [{name=alpha, opt1=1, opt2=foo}]

However, calling cli --opt1=1 results in [{name=null, opt1=2}], with no error. I’d expect an error since the group name is required but not provided, but that doesn’t seem to be the case. Is this supported?

[remkop]

I have been able to reproduce the issue and found the cause: a bug in the validation logic.

[remkop]

@wjohnson5 Thanks for that background. A feature like this (“repeatable subcommands” https://github.com/remkop/picocli/issues/454 ) is on the TODO list but has been shelved until a clear use case comes up. On the surface it does not look that hard to implement but I haven’t spent the time to analyse in depth. The Click documentation is certainly helpful.