go-flags

I've become a fan of https://github.com/jessevdk/go-flags (also enjoyed structopt which is similar for Rust). I much prefer defining the flags statically on a type which stores them after rather than building it all up programmatically. Otherwise, I'm not really sure what this offers that alternatives don't, apart from the -a 1 2 3 -> [1,2,3] business which seems highly confusing and undesirable to me so I'd think of it as more of an anti-feature.

Hello everyone, I've just released three different libraries aimed at either enhancing or facilitating CLI application development. Flags (https://github.com/reeflective/flags) flags aims to merge the concepts from https://github.com/jessevdk/go-flags, and https://github.com/octago/sflags, both relying on struct tags to define CLI command specs. The flags library uses these underlying concepts to produce complete `cobra.Command` trees, and brings many comfort-of-life improvements for the generated applications/commands. Console (https://github.com/reeflective/console) This library wraps the readline library (described below) and leverages cobra commands in order to provide a closed-loop console working with cobra commands out of the box, also providing many comfort-of-life features at minimum cost, like support for oh-my-posh prompt engin

I liked go-flags https://github.com/jessevdk/go-flags

Not really a fan of this approach. I don't like the duality between the help text and the struct it gets bound to - much prefer the approach of generating the help text from a struct. https://github.com/jessevdk/go-flags is my favourite option; it's lightweight but amazingly featureful, and I much prefer the declarative approach to a programmatic one like the standard library flags package

For my purpose, go-flags was a great fit. https://github.com/jessevdk/go-flags

I like https://godoc.org/github.com/jessevdk/go-flags, since it also supports environment variables. It's nice to be able to get configurable defaults from the environment and still be able to override them on the command line.

Go isn't immune to the problem either. See the `flag` package, which is something that new users are encouraged to avoid in favor of e.g. https://github.com/jessevdk/go-flags .

I always use go-flags [1] in my Go programs. It has support for GNU-style options, pretty help output, subcommands, automatic parsing of more complex arguments (e.g. time.Duration) among other things. I do wish they would improve the included flags package though. There are lots of nice third party packages, but having a proper one in the standard library would've been better. [1] https://github.com/jessevdk/go-flags

You don't have to use flag package from the stdlib, there a are plenty of others, eg: https://github.com/jessevdk/go-flags