Arguably

--option`s are now able to be configured four different ways:

* `[-o]` → `-o` is the short name
* `[--option]` → `--option` is the long name
* `[-o/--option]` → `-o` is the short name, `--option` is the long name (this can also be `[--option/-o]`)
* `[-o/]` → `-o` is the short name, the default long name is *removed*.

Additionally, there are now warnings if this sort of format is incorrectly specified.

**Full Changelog**: https://github.com/treykeown/arguably/compare/v1.2.4...v1.2.5

In addition to `argparse`-related calls, function invocations for `arguably.command` are now also logged. This can be seen if using `python3 -m arguably --debug your_script.py`, or if you set up logging in your script that utilizes `arguably`.

This was intended behavior from the start, but was not implemented.

**Full Changelog**: https://github.com/treykeown/arguably/compare/v1.2.3...v1.2.4

Allows long option names to be overriden - instead of writing the docstring as `some_arg: [-s]`, write it as `some_arg: [-s/--long-name]`

**Full Changelog**: https://github.com/treykeown/arguably/compare/v1.2.2...v1.2.3

arguably` will now fail much faster if a bad configuration is given to `arguably.command`. The validation logic was shifted around to fix some cases that caused `arguably` to fail if invoked directly on a script via `python3 -m arguably your_script.py`.

**Full Changelog**: https://github.com/treykeown/arguably/compare/v1.2.1...v1.2.2

This release adds support for decorating `async` functions with `arguably.command`.

**Full Changelog**: https://github.com/treykeown/arguably/compare/v1.2.0...v1.2.1