You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, specifying subcommands requires you to manually insert them into the Command struct, commonly done via
Command{subcommands:vec![a(), b(), c()],
..foo()}
which is quite cumbersome, especially if you're splitting up your commands into separate modules.
To improve this, I'd propose adding a subcommands attribute to the poise::command macro, which would allow specifying subcommands on the parent command like this:
Currently, specifying subcommands requires you to manually insert them into the Command struct, commonly done via
which is quite cumbersome, especially if you're splitting up your commands into separate modules.
To improve this, I'd propose adding a
subcommands
attribute to thepoise::command
macro, which would allow specifying subcommands on the parent command like this:The text was updated successfully, but these errors were encountered: