The cli library is meant to make it easy to create command line utilities of your own.
A CLI handles parsing all the command-line flags, options and arguments and instantiates a Plugin to process the command.
A CLI may support multiple Plugin's in which case the first argument is used to determine which to run (or if no arguments, the default plugin will be selected) or may be designed to be standalone, in which case exactly one Plugin will be used and no command argument is allowed.
Add a plugin class for the command. After all options and flags have been consumed, the first argument will be consumed and the associated plugin class will be instantiated and run.
Set a dedicated Plugin class which will handle all input. This may not be used in conjunction with addPlugin and will not automatically accept a command from the arguments.
Shows the usage help screen for the CLI and terminates.
Usually the value of args passed in will be
Each Plugin manages each command of a CLI and is executed in phases.
If the usage (i.e. help) of a CLI is requested, the static methods
getOptionHelp are used to generate the help screen.
Otherwise, a plugin is instantiated and the
prepareOptions is called. Each plugin must call
super.prepareOptions, otherwise the basic options are not yet processed. During this time a Plugin should consume all the flags and options it understands, since any left over flags or options will cause the CLI to bail and issue an unknown option error. This should throw if a value for a given option is invalid or some combination of options and flags is not allowed.
Once the prepareOptions is complete (the returned promise is resolved), the
prepareArguments is called. This should validate the number of arguments expected and throw an error if there are too many or too few arguments or if any arguments do not make sense.
Once the prepareArguments is complete (the returned promise is resolved), the
run is called.
The network this plugin is running for.
The provider for this plugin is running for.
The accounts passed into the plugin using
--account-void which this plugin can use.
The gas limit this plugin should use. This is null if unspecified.
The gas price this plugin should use. This is null if unspecified.
The initial nonce for the account this plugin should use.
A plugin should use this method to resolve an address. If the resolved address is the zero address and allowZero is not true, an error is raised.
Dumps the contents of info to the console with a header in a nicely formatted style. In the future, plugins may support a JSON output format which will automatically work with this method.
Stops execution of the plugin and shows the help screen of the plugin with the optional message.
Stops execution of the plugin and shows message.
Each subclass should implement this static method which is used to generate the help screen.
Each subclass should implement this static method if it supports additional options which is used to generate the help screen.
The ArgParser is used to parse a command line into flags, options and arguments.
Flags are simple binary options (such as the
--yes), which are true if present otherwise false.
Options require a single parameter follow them on the command line (such as
--account wallet.json, which has the name
account and the value
Arguments are all other values on the command line, and are not accessed through the ArgParser directly.
When a CLI is run, an ArgParser is used to validate the command line by using prepareOptions, which consumes all flags and options leaving only the arguments behind, which are then passed into prepareArgs.
Remove the flag name and return true if it is present.
Remove all options which match any name in the Array of names with their values returning the list (in order) of values.
Remove the option with its value for name and return the value. This will throw a UsageError if the option is included multiple times.
Remove all options with their values for name and return the list (in order) of values.