treykeown

This is necessary if you want to skip parsing args, and just display the help or version.

Would be great to have a splash of color. However, color should be [automatically disabled if output is piped to a different application](https://no-color.org/). Also, can we make the usage and...

Implement config interface

1

Loading configuration is a very common pattern for CLIs - we need a way to do this. Design should use something like `arguably.arg.config()` and use the values in there to...

Take inputs from environment variables

1

This isn't an uncommon pattern - could be useful to allow some parameters to take their input from an environment variable. There are some unresolved questions around naming, though: 1....

There could be reasons to make a boolean input either be required, or optional as with a `bool | None` typed parameter. In that case it could be helpful to...

Would need some extra work here - the `Flag` system is a little brittle. Would need to make the `Enum`s mutually exclusive.

Currently, `arguably` is based on `argparse`. However, `click` has a much nicer interface and we may be able to interoperate with it, as `typer` does. 1. Should `argparse` be completely...

Currently, `arguably` is designed to only be run once. It might be useful to allow global state to persist. Doing so would require examining all the state in `_context.Context` and...