Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tagged Commands #14

Open
coreybutler opened this issue Oct 14, 2022 · 0 comments
Open

Tagged Commands #14

coreybutler opened this issue Oct 14, 2022 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@coreybutler
Copy link
Member

As I've used this library to build applications, I've recognized a need for experimental commands, beta commands, and even hidden commands (hidden from help).

It would be nice to have a "tag" or some other identifier to identify which commands are experimental, which should be hidden, etc.

One possible implementation is:

new Command({
  name: 'cmd',
  tags: ['beta'],
  async handler () {...}
})

Special tags may have special documentation/help features:

  • hidden: available, but does not show up
  • ignore: completely ignore the command (won't run)
  • experimental: prefixes description with EXPERIMENTAL.
  • deprecated: prefixes description with DEPRECATED.

Tags should be exposed to command handlers and directly through the shell, making it possible for developers to create custom functionality for tagged commands.

Please use the reactions to cast a vote in favor of or against this feature suggestion »
@coreybutler coreybutler added the enhancement New feature or request label Oct 14, 2022
@coreybutler coreybutler self-assigned this Oct 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant