cmdargs

cmdargs copied to clipboard

Add the ability to define arbitrary Flag values in Implicit mode

1

Sometimes it is useful to define one flag as entirely custom, e.g. by fully specifying the `Flag` value. I should support that.

ndmitchell

I suspect it is never used by anyone, and it introduces an unfortunate dependency. I should try and eliminate it.

ndmitchell

People seem to like writing their parsers in applicative format. I'm not a fan (you don't write the label next to the value, which makes it fragile) but I should...

ndmitchell

an optional value is not parsed as part of the option if separated from the flag by a space

1

Eg https://github.com/simonmichael/hledger/issues/149 .

simonmichael

yaitskov

When deriving option _names_ from constructors, underscore is converted to '-' using `asName` [function](https://github.com/ndmitchell/cmdargs/blob/29acda060190f18e739027d841badaaa1329e440/System/Console/CmdArgs/Implicit/Global.hs#L232C1-L232C7). The same logic should apply when deriving _values_ for options of algebraic types. A canonical scenario...

sapek

In Liquid Haskell, the help messages for each flag are rather narrow. ``` liquidhaskell [OPTIONS] Refinement Types for Haskell Common flags: --minimal Minimal logging verbosity -q --quiet Silent logging verbosity...

facundominguez