Desertbit/grumble: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
 
(One intermediate revision by the same user not shown)
Line 23: Line 23:


==Option 2==
==Option 2==
In this case, a flag '''must''' be registered, even if it has a zero value, otherwise the attempt to get the flag will panic the runtime.


<syntaxhighlight lang='go'>
<syntaxhighlight lang='go'>
flags := map[string]*grumble.FlagMapItem{
flags := map[string]*grumble.FlagMapItem{
"arg1":    flagValue(arg1),
"arg1":    return &grumble.FlagMapItem{Value: arg1},
"arg2":    flagValue(arg2),
"arg2":    return &grumble.FlagMapItem{Value: arg2},
}
}
ctx := &grumble.Context{
ctx := &grumble.Context{

Latest revision as of 19:23, 6 November 2024

External

Internal

Overview

Unit Testing Commands

These options do not capture the command output, just side effects:

Option 1

command := somepackage.SomeCommand(...)
app := grumble.New(&grumble.Config{Name: "test"})
app.AddCommand(command)
args := []string{
    "somecommand",
    "--arg1", "test1",
    "--arg2", "test2",
}
err := app.RunCommand(args)

Option 2

In this case, a flag must be registered, even if it has a zero value, otherwise the attempt to get the flag will panic the runtime.

flags := map[string]*grumble.FlagMapItem{
	"arg1":    return &grumble.FlagMapItem{Value: arg1},
	"arg2":    return &grumble.FlagMapItem{Value: arg2},
}
ctx := &grumble.Context{
	Flags:   flags,
	Context: context.Background(),
}
command := somepackage.SomeCommand(...)
err := command.Run(ctx)

Capture and Test Output