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
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.
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 »
The text was updated successfully, but these errors were encountered:
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:
Special tags may have special documentation/help features:
hidden
: available, but does not show upignore
: completely ignore the command (won't run)experimental
: prefixes description withEXPERIMENTAL.
deprecated
: prefixes description withDEPRECATED.
Tags should be exposed to command handlers and directly through the shell, making it possible for developers to create custom functionality for tagged commands.
The text was updated successfully, but these errors were encountered: