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
If called with keyword arguments, the key should be used as the name of the attribute added to the Group subclass.
The function should update __feud_commands__ on the subclass, and any other relevant attributes. It should probably check that there isn't already a class member with the same name.
If a function is provided, it should be wrapped with @feud.command(config=cls.__feud_config__).
The text was updated successfully, but these errors were encountered:
Note: If the user is permitted to call Group.add_command on a click.Group, the following should change to include objects in cls.commands() which are click.Groups.
Does this suggestion already exist?
Feature description
Currently commands must be specified as members of a
Group
subclass when the subclass is defined, i.e.:In some cases, it may be useful to define the group first, then add the command later, e.g.:
Where
func1
/func2
may be a function, or aclick.Command
generated from@feud.command
/@click.command
/@click.group
.Proposed signature is:
If called with keyword arguments, the key should be used as the name of the attribute added to the
Group
subclass.The function should update
__feud_commands__
on the subclass, and any other relevant attributes. It should probably check that there isn't already a class member with the same name.If a function is provided, it should be wrapped with
@feud.command(config=cls.__feud_config__)
.The text was updated successfully, but these errors were encountered: