Releases: akamensky/argparse
Releases · akamensky/argparse
v1.4.0
v1.3.3
v1.3.2
What's Changed
- Fix coverage reporting by @akamensky in #101
- Flag ignores default value by @akamensky in #103
- Flag counter usage fix by @Alec-Bakholdin in #100
- When subcommand must be present but not provided the error must be triggered by @akamensky in #104
Full Changelog: v1.3.1...v1.3.2
Contributors
akamensky and alecbakholdin
Assets 2
Bugfixes
v1.3.0: Arg can return the result pointer (#84)
* Arg interface can return result pointer * Arg interface can return result pointer * Add examples & documentation * add docstring Co-authored-by: verburgs <joshua.verburg-sachs@hpe.com> Co-authored-by: vsachs <vsachs@hpe.com>
v1.2.2: sub-command-help (#72)
v1.2.1: Bugfixes
add a boolean flag to message2string which indicates if the result st… …ring is ready to be returned + add tests (#60)
v1.2.0: Custom help (#50)
* Finishes addressing issue #29 Adds a Settings struct for creating parsers/commands with NewParserWithSettings or NewCommandWithSettings. Settings HelpDisabled - defaults false, set true to not generate a help argument for parser/command HelpSname - short name for the parser/command help argument. Can be left empty HelpLname - long name for the parser/command help argument. Leaving empty forces use of -h/--help when HelpDisabled is false NoExitOnHelp - defaults false, set true to not exit on help argument being parsed Should resolve all outstanding help argument issues. * Finishing Issue #29 Fixed merge conflict error due to check function return type change confusion. * Updated Settings Object to multiple function calls Added functions: DisableHelp SetHelp ExitOnHelp Added Command.exitOnHelp Added more tests to increase code coverage * Updated no help example