* I need to stop rewriting builtin methods with reduce.
* Removed redundant fields from the config class.
* Added a warning when module version and beau.yml version differ.
* Moved the spinner initialization to the base class.
* Got rid of the base class, it complicated testing.
Now it lives on as a utils file. Should make it easier to test the CLI.
* Added a spec file for the ListCommand.
* Added tests for all CLI commands.
* Update some old tests.
Added missing cases and tests.
Most of these are kind useless but I hope I won't have to touch them
again.
--as-json outputs the response as json, this allows you to use tools
like jq on the output which is nice.
--quiet makes it so no output is printed. I added this in case you are
looping Beau and don't want to see the output of every single request.
Example: `seq 10 | xargs -I{} beau request hi --quiet`.
I am making a couple of small changes to how external environment
variables are used. From now own everything comming from the outside,
namely the .env file and the params flag are assigned to the '_'
variable within the internal environment. This is mostly to namespace
things and make it clear where they are coming from.
This is mostly some clean up. Now plugins are checked for existence
before being required. The regex for dynamic values was improved a
little in an attemp to make it more reliable. Plugins are only required
once now.
The CLI's CWD is set to that of the config file. This makes relative
paths mentioned in the file more reliable.
* Added a schema validator.
This allows you to check if the given beau config is valid. Will be used
to improve the CLI and remove schema validation-type errors from the
actual code.
* Added a validate command to the CLI.
This command is a way to test the config file. Eventually it'll probably
be removed and the schema validation will run on every other command. I
have to determine how useful this is and how performance might be
affected.
This introduces a top level key: `hosts`. It's an array where you can
configure multiple hosts with their own requests, they share defaults
and environment with the global scope.
This allows you to have multiple paths being the same with different
endpoints and settings.
David Díaz