| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-06-27 | fix discrepancy in order of arguments for Func() and BoolFunc() #433 | Georges Varouchas | |
| for no good reason: the order of arguments would differ when calling pflag.BoolFuncP(...) and (*FlagSet).BoolFuncP(...) (same goes for Func() and FuncP()) in this commit: align all functions on stdlib's order fixes #433 | |||
| 2025-06-09 | fix help message for Func and BoolFunc flags #430 | Georges Varouchas | |
| * have '.Type()' for boolfuncValue return "boolfunc" (dedicated value, which now makes it distinct from funcValue) * hide extra "(default )" by stating that "" should be treated as a zero value for a boolFlag note: - a boolfuncValue matches 'case boolFlag:', as it implements the boolFlag interface, - treating "" as a value which shouldn't trigger a "(default )" for a regular Bool flag does not look like a breaking change * hide extra "[=something]" for boolfuncValue * set default placeholder name for "boolfunc" and "func" flag types | |||
| 2025-05-22 | add support for Func() and BoolFunc() #426 | Georges Varouchas | |
| Add support for two features which landed in the 'flag' package from the standard library: Func() and BoolFunc() and their two pflag specific versions: FuncP() and BoolFuncP() fixes #426 | |||
