You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLI guidelines suggestion the following convention for named arguments:
Every short flag must have long version as well
Don’t have ambiguous or similarly-named commands. For example, having two subcommands called “update” and “upgrade” is quite confusing. You might want to use different words, or disambiguate with extra words.
The given parser doesn't try to parse pre-defined parsers: --help, --version, --numeric-version, etc.
Is it possible to check such things with optparse-applicative? 🤔
The text was updated successfully, but these errors were encountered:
Hi, its possible to check all three points. In optparse-applicative-common are low level function which can be used to check all three points. mapParser (\_ x -> optionNames . optMain $ x) sampleParser gives the list of defined parsers.
CLI guidelines suggestion the following convention for named arguments:
--help
,--version
,--numeric-version
, etc.Is it possible to check such things with
optparse-applicative
? 🤔The text was updated successfully, but these errors were encountered: