ff
warg
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ff
-
What is the most common approach to configure a backend app?
We have been using https://github.com/peterbourgon/ff for long time now. It combines the standard flags with the environment variables nicely.
- Which packages do you recommend for building cli tools?
-
Best practice for configuring secrets
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
-
I'm looking for a good alternativ to Viper
Have a look at https://github.com/peterbourgon/ff
- I created my own config manager package because others seemed too complex and full of features that I'm never going to use.
- How do you manage your service configuration?
-
Go modules are soon going to be the only future
Here are the tags and the branches for one of my repos, which has seen major version 1, 2, and 3 so far.
warg
-
An Efficient Struct Configuration Pattern For Golang
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
-
Which packages do you recommend for building cli tools?
I wrote my own! https://github.com/bbkane/warg/
-
Major standard library changes in Go 1.20
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
-
Have you used generics?
I'm using to allow for custom flag types in my CLI parsing library- a lot less duplicate code
-
Go: Functional Options Are Slow
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
-
How are YOU using generics so far?
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!
-
Unix command line conventions over time
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/ .
What are some alternatives?
go-envconfig - A Go library for parsing struct tags from environment variables.
graph - A library for creating generic graph data structures and modifying, analyzing, and visualizing them.
conf - Package conf provides support for using environmental variables and command line arguments for configuration.
cli-guidelines - A guide to help you write better command-line programs, taking traditional UNIX principles and updating them for the modern day.
cleanenv - ✨Clean and minimalistic environment configuration reader for Golang
workgroup - Structured concurrency manager for Go
xflags - Expressive flags for Go
golang-generics-dao-example - Example using Generics with DAO
go-yamlcfg
scan - Scan provides the ability to to scan sql rows directly to any defined structure.
kong - Kong is a command-line parser for Go
RCIG_Coordination_Repo - A Coordination repo for all things Rust Cryptography oriented