From the discussion on #57 it is clear that it would be useful if extended help annotations could be placed on a @Cli annotated class and automatically propagated to all commands placed into that CLI.
The basic design would be that when creating a CLI from an annotated class we would discover extended help annotations on that class and convert these to help sections. Then when adding commands into the CLI we will use those sections as a base for each commands extended help. As is already possible commands could still declare their own extended help annotations which would override the top-level declarations.
Ideally it should also be possible to do something similar when using the CliBuilder API
From the discussion on #57 it is clear that it would be useful if extended help annotations could be placed on a
@Cliannotated class and automatically propagated to all commands placed into that CLI.The basic design would be that when creating a CLI from an annotated class we would discover extended help annotations on that class and convert these to help sections. Then when adding commands into the CLI we will use those sections as a base for each commands extended help. As is already possible commands could still declare their own extended help annotations which would override the top-level declarations.
Ideally it should also be possible to do something similar when using the
CliBuilderAPI