Jonas mg
Jonas mg
``` type let struct { a foo } ``` The failure is because it tries gets a type which has not been yet created, which is valid in Go. This...
Yes, there is an issue in the history. But I have no time to fix it. Sorry! Anyway, I accept code that could fix it.
@ElPincheTopo Yes, I'd accept them.
I guess so but the idea was to have the same output for when someone want to add a section of examples.
> > Although I want to check to see if anyone else in @urfave/cli also thinks this is a good idea? Since I know we've had some concerns about there...
> HTTP solves a complex problem, as does a CLI library, so the number of knobs we end up with is definitely a product of that complexity. But part of...
> A few of the problems with having too many fields: > > * More code for library authors to maintain/test > * Commitment to backward compatibility—we can't easily undo...
@lynncyrin At the main help of the command, there is a section called `COMMANDS` where you could have a command with sub-commands, and I think that would be very well...
The main help of a tool could be like this one: ``` ./foo -h NAME: foo - Tool to ... USAGE: foo [global options] command [command options] [arguments...] VERSION: 1.0.0...
I like that output, where you see from the main help all commands and sub-commands.