BSD-3-Clause licensed by Gabriella Gonzalez
This version can be pinned in stack with:optparse-generic-1.5.2@sha256:acdd6557ab1489f26df46c07fab530f92f83cba1da0a15c510e820d8cea516a4,2337
Module documentation for 1.5.2
Depends on 11 packages
(full list with versions):
base,
bytestring,
filepath,
Only,
optparse-applicative,
optparse-generic,
text,
time,
transformers,
transformers-compat,
void This library auto-generates an optparse-applicative
-compatible
Parser
from any data type that derives the Generic
interface.
See the documentation in Options.Generic
for an example of how to use
this library
1.5.2
1.5.1
1.5.0
1.4.9
1.4.8
1.4.7
1.4.6
- Use
readField
in default implementation of parseField
1.4.5
1.4.4
readIntegralBounded
: use metavar
in error message
1.4.3
- Export internal
readIntegralBounded
utility
- Build against
optparse-applicative-0.16.0.0
1.4.2
- New
unwrap
function
- This is the underlying utility that powers
unwrap{Record,RecordPure,WithHelp}
1.4.1
1.4.0
- BREAKING CHANGE: Add support for type-level default values
- This is a breaking change because the various
parse*
typeclass methods
now take an additional argument to support this feature
1.3.1
- Export
GenericParseRecord
and getRecord{,PureWith}
1.3.0
- BREAKING CHANGE: New
metavar
method for ParseField
class
- This field simplifies customizing
ParseField
instances
- Now you usually only need to override
metavar
now or possibly also
readField
, whereas the default behavior for parseField
should work
more often
- This is only a breaking change for data types that use the default
implementation of
ParseField
but do not derive Typeable
- You can migrate existing code that doesn’t compile by just explicitly
specifying what the
metavar
field should be