No documentation for top level flags about subcommands HOT 5 OPEN

I've been trying to figure out the best way to use the top level flags myself.

from subcommands.

After looking into this more and looking into projects that include this, I believe this is referring instead to the flags that are explicitly defined with the flags package. They exist outside the configuration of this package, which is why they must come first. They also need to be plumbed in directly since they reside in the main package.

At least I think that's how it works.

from subcommands.

Yes, from what I recall you at correct. I think the confusion is coming from the comment calling these 'top-level flags', that simply means they are not treated as subcommands but instead parsed using flags.Parse(). Subcommands don't have direct access to these flags other than through normal channels like top level variables.

from subcommands.

Suggested example: https://play.golang.org/p/BGV9lVDjIc5

from subcommands.

Another way of looking at it, after spending some time creating a tutorial for this package (see https://github.com/fgm/subcommands_demo ): after parsing, add the parsed value to the context, like:

// package scope
type verboseKey string
// function scope
flag.BoolVar(&verbose, "v", false, "make it verbose)
fs.Parse()
ctx = context.WithValue(ctx, verboseKey("v"), verbose)
subcommands.Execute(ctx)

At this point your command can retrieve the flag value from the context without sharing a variable using ctx.Value(verboseKey("v")).(bool). Which makes sense, as a CLI run is pretty much like a request on a server.

You could also pass the value using the extra args, like subcommands.Execute(ctx, verbose) and in the command, retrieve it as args[0].(bool), but that seems a little less robust and less semantically appropriate.

from subcommands.