ff VS warg

We have been using https://github.com/peterbourgon/ff for long time now. It combines the standard flags with the environment variables nicely.

Tho, its also very common to use flags as they add documentation. You can use a mix of both. Maybe something in the lines of https://github.com/peterbourgon/ff

Have a look at https://github.com/peterbourgon/ff

Here are the tags and the branches for one of my repos, which has seen major version 1, 2, and 3 so far.

Funcopts aren't always appropriate, but boy do they make things more readable sometimes. I use them pervasively in warg to allow declarative nested CLI commands

I wrote my own! https://github.com/bbkane/warg/

Very useful! I'll be playing with the error tree additions and studying the HTTP interface extension to see if I can replicate the pattern for https://github.com/bbkane/warg values. Id like to be able to have value-specific output for different types of --help , even ones not in warg

I'm using to allow for custom flag types in my CLI parsing library- a lot less duplicate code

One thing that I find nicer with functional options is building tree-like data structures.

My command line parsing library uses them to declaratively build CLI apps with arbitrarily nested subcommands.

Some examples at https://github.com/bbkane/warg/tree/master/examples

I'm writing a CLI parsing library, and generics have let me consolidate most of the flag value functionality for different types. So the flags for dbz --level 9000 --type superSaiyan share most of the same code even though one is an int and one is a string. So much fewer copy-paste-modify lines of code now!

This is largely what the Azure CLI does. It simplifies even further by eliminating the no-value option. Instead, you pass "true" or "false" as the value ( --example true ). It's a little more verbose but very easy to parse/write/generate. I like this convention so much I stole it for my homemade Golang CLI parsing library https://github.com/bbkane/warg/ .