is it possible to have subcommands (Command) and args inside ArgGroup?

[Masber]

Hi,
I am building a CLI using clap, and I was thinking of doing something like the below:

$ mycli get meal <meal name>
$ mycli get --meal <meal name>
$ mycli get dessert <dessert name>
$ mycli get --dessert <dessert name>
$ mycli get drink <drink name>
$ mycli get --drink <drink name>
$ mycli get meal <meal name> drink <drink name> get dessert <dessert name>
$ mycli get mean <meal name> dessert <dessert name>
...

The point is, I would like to offer the option of using args or subcommands to introduce the values...

I tried this

    let cli_root = Command::new("mycli")
        .arg_required_else_help(true)
        .subcommand(
            Command::new("get")
                .subcommand(Command::new("MEAL").arg(arg!(<MEAL> "Get meal")))
                .subcommand(Command::new("DRINK").arg(arg!(<DRINK> "Get drink")))
                .arg_required_else_help(true)
                .arg(arg!(-m --meal <FOOD> "Get meal"))
                .arg(arg!(-d --drink <DRINK> "Get drink"))
                .groups([
                    ArgGroup::new("meal_subcommand").arg("MEAL"),
                    ArgGroup::new("drink_subcommand").arg("DRINK"),
                    ArgGroup::new("meal_arg").arg("meal"),
                    ArgGroup::new("drink_arg").arg("drink"),
               )]

Without success because the compiler complains about

thread 'main' panicked at 'Command get: Argument group 'meal_subcommand' contains non-existent argument 'MEAL'', ...clap-4.0.32/src/builder/debug_asserts.rs:309:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I would like to ask if it is possible to use Command inside a GroupArg, if now how could I achieve this?

[epage]

Subcommands cannot be used at this time in arg groups. We tried to clarify this in clap v4 with "name" vs "id". We we work to allow more customization in clap (#3476), people will be able to have better control over situations like this.

However, I wonder if args_conflicts_with_subcommands is sufficient for your case. See the git-derive example