| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-05-14 | fix #423 : Add helper function and some documentation to parse shorthand go ↵ | Andrea Tarocchi | |
| test flags. | |||
| 2018-04-03 | make x.Parsed() return true after AddGoFlagSet(x) and pflag.Parse() (#162) | childe | |
| * make GoFlagSets.Parsed() true after pflag.Parse some third part lib such as glog use go flag package, and its some actions depends on if goflag.Parsed(). * add test case for goflag.CommandLine.Parsed() * add comment to goflag.CommandLine.Parsed test case | |||
| 2015-08-16 | Add functions to support golang flags in pflags | Eric Paris | |
| They aren't "perfect". spf13/pflag chose to use an explicit `Type` in the value. golang has nothing of the sort and has a rather crazy IsBoolFlag() bit of nonsense for the one case that really makes sense to have the explicit `Type`. Probably because adding interfaces really screws people up. So supporting golang flags in pflags isn't super super simple, we need to figure out how to handle our `Type` given only the information available in a golang flag. This does it as best we can with `reflect`. | |||
 |
index : github.com/spf13/pflag.git | |
| Drop-in replacement for Go's flag package, implementing POSIX/GNU-style --flags |
| aboutsummaryrefslogtreecommitdiff |
path: root/golangflag_test.go