Allow for passing around context with cli about cli HOT 3 CLOSED

I've been solving this by actually passing the context into the Command implementations. This removes the nasty interface{} type unsafety you might get with contexts. example:

struct MyCommand {
  Config *MyConfig
}

func (c *MyCommand) Run(args []string) int {
  c.Config usage here
}

Thoughts?

from cli.

That's how I ended up solving. Looking through your code for Serf though,
how does Ui get passed into most the command that are initialized with
&command.JoinCommand {}?

On Tue, Nov 5, 2013 at 1:34 PM, Mitchell Hashimoto <[email protected]

wrote:

I've been solving this by actually passing the context into the Commandimplementations. This removes the nasty
interface{] type unsafety you might get with contexts. example:

struct MyCommand {
Config *MyConfig}
func (c *MyCommand) Run(args []string) int {
c.Config usage here}

Thoughts?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-27799426
.

from cli.

Ah, I think you saw the old Serf code. I extracted this cli lib from Packer and Serf but had to rework it a bit to be more general. That was one of the changes. Take a look at Serf now. :)

from cli.