3 ms·
I try to write all my CLIs this way - to the point of writing my own Go CLI parsing library [0] to do it. Now, when I run `cmd -h`, I get output like the follo
by bbkane 3y ago
I try to write all my CLIs this way - to the point of writing my own Go CLI parsing library [0] to do it.
Now, when I run `cmd -h`, I get output like the following for all flags (example from [1]):
--count , -c : Number of times to dig
type : int
default : 1
configpath : dig.combine.count
required : true
currentvalue (set by config) : 1
It's sometimes more verbose than I'd like, but it's quite useful for figuring out how a flag got its current value
[0] https://github.com/bbkane/warg https://github.com/bbkane/warg
[1] https://github.com/bbkane/shovel https://github.com/bbkane/shovel