William Rusnack

pull #31 and #32 before this closes #7 This allows for more flexibility for parsing the command line arguments by not converting the cli args into the State data. Does...

do not pull befor #35 Allows for alternative env var names to use the same handler. Does have breaking changes with `data Env :: Optionality -> [Symbol] -> * ->...

ensure #33 is pulled This allows multiple arguments to be consumed with multiple container types. Does use unsafeCoerce because I am unsure how to correctly handle some type transformations. If...

do not pull before #35 Allows multiple flag keys to be specified for the same flag handler like the example extended and shortened flags `~~flag` and `~f` that would both...

do not pull before #33 Allows multiple option keys to be specified for the same option handler like the example extended and shortened option keys `--abcd ` and `-a `...

Perhaps just put under `where` or add signature. ```text app/Task/CLI.hs:45:1: warning: [-Wmissing-signatures] Top-level binding with no type signature: editTask :: FilePath -> ProgramT (Annotated annotation (Arg "task-name" String) & Raw)...

There were too many changes happening at once in the previous commits. This organizes the module Options.Commander into multiple modules to isolate functionality. Most of the other PRs will build...

All the tests have been converted over to use hspec. Matches the module structure introduced with #31 .

right is usually tried first

4

Maybe I am mistaken but isn't usual to have the right be tried first? https://github.com/SamuelSchlesinger/commander-cli/blob/51116f5e9b4f40cb8ba3eacf45cf801fab102180/src/Options/Commander.hs#L185

toplevel -h --help

1

accept the typical help commands of -h and --help to show the documentation