urfave/cli v1.20.0 Release Notes
Release Date: 2017-08-11 // over 6 years ago-
๐ Fixed
HandleExitCoder
is now correctly iterates over all errors in aMultiError
. The exit code is the exit code of the last error or1
if there are noExitCoder
s in theMultiError
.- ๐ Fixed YAML file loading on Windows (previously would fail validate the file path)
- Subcommand
Usage
,Description
,ArgsUsage
,OnUsageError
correctly propogated ErrWriter
is now passed downwards through command structure to avoid the need to redefine it- Pass
Command
context intoOnUsageError
rather than parent context so that all fields are avaiable - ๐จ Errors occuring in
Before
funcs are no longer double printed - ๐ Use
UsageText
in the help templates for commands and subcommands if defined; otherwise build the usage as before (was previously ignoring this field) IsSet
andGlobalIsSet
now correctly return whether a flag is set if a program callsSet
orGlobalSet
directly after flag parsing (would previously only returntrue
if the flag was set during parsing)
๐ Changed
- No longer exit the program on command/subcommand error if the error raised is
not an
OsExiter
. This exiting behavior was introduced in 1.19.0, but was determined to be a regression in functionality. See the PR for discussion.
โ Added
CommandsByName
type was added to make it easy to sortCommand
s by name, alphabeticallyaltsrc
now handles loading of string and int arrays from TOML- ๐ Support for definition of custom help templates for
App
viaCustomAppHelpTemplate
- ๐ Support for arbitrary key/value fields on
App
to be used withCustomAppHelpTemplate
viaExtraInfo
HelpFlag
,VersionFlag
, andBashCompletionFlag
changed to explictly becli.Flag
s allowing for the use of custom flags satisfying thecli.Flag
interface to be used.