Advanced
The [Basics] showed how to access arguments for a command. They are all retrieved as strings which is fine
but it we need to say get integers or timestamps the user would have to convert from string to desired type.
To ease the burden on users the cli library offers predefined {Type}Arg and {Type}Args structure to facilitate this.
The value of the argument can be retrieved using the command.{Type}Arg() function. For e.g
package main
import (
"fmt"
"log"
"os"
"context"
"github.com/urfave/cli/v3"
)
func main() {
cmd := &cli.Command{
Arguments: []cli.Argument{
&cli.IntArg{
Name: "someint",
},
},
Action: func(ctx context.Context, cmd *cli.Command) error {
fmt.Printf("We got %d", cmd.IntArg("someint"))
return nil
},
}
if err := cmd.Run(context.Background(), os.Args); err != nil {
log.Fatal(err)
}
}
Running this program with an argument gives the following output
$ greet 10
We got 10
Instead of using the cmd.{Type}Arg() function to retrieve the argument value a destination for the argument can be set
for e.g
package main
import (
"fmt"
"log"
"os"
"context"
"github.com/urfave/cli/v3"
)
func main() {
var ival int
cmd := &cli.Command{
Arguments: []cli.Argument{
&cli.IntArg{
Name: "someint",
Destination: &ival,
},
},
Action: func(ctx context.Context, cmd *cli.Command) error {
fmt.Printf("We got %d", ival)
return nil
},
}
if err := cmd.Run(context.Background(), os.Args); err != nil {
log.Fatal(err)
}
}
Some of the basic types arguments supported are
FloatArgIntArgInt8ArgInt16ArgInt32ArgInt64ArgStringArgUintArgUint8ArgUint16ArgUint32ArgUint64ArgTimestampArg
This is ok for single value arguments. Any number of these single value arguments can be concatenated in the Arguments
slice field of Command.
Single value arguments are optional by default. If the argument is not provided the default Value is used instead.
You can mark a single value argument as required by setting the Required field to true. If a user does not
provide a required argument, they will be shown an error message.
Required single-value arguments should be declared before optional or multi-value arguments because arguments are consumed in declaration order.
package main
import (
"context"
"fmt"
"log"
"os"
"github.com/urfave/cli/v3"
)
func main() {
cmd := &cli.Command{
Arguments: []cli.Argument{
&cli.IntArg{
Name: "someint",
Required: true,
},
},
Action: func(ctx context.Context, cmd *cli.Command) error {
fmt.Printf("We got %d", cmd.IntArg("someint"))
return nil
},
}
if err := cmd.Run(context.Background(), os.Args); err != nil {
log.Fatal(err)
}
}
The library also support multi value arguments for e.g
package main
import (
"fmt"
"log"
"os"
"context"
"github.com/urfave/cli/v3"
)
func main() {
cmd := &cli.Command{
Arguments: []cli.Argument{
&cli.IntArgs{
Name: "someint",
Min: 0,
Max: -1,
},
},
Action: func(ctx context.Context, cmd *cli.Command) error {
fmt.Println("We got ", cmd.IntArgs("someint"))
return nil
},
}
if err := cmd.Run(context.Background(), os.Args); err != nil {
log.Fatal(err)
}
}
Some things to note about multi value arguments
- They are of
{Type}Argstype rather than{Type}Argto differentiate them from single value arguments. - The
Maxfield needs to be defined to a non zero value without which it cannot be parsed. Maxfield value needs to be greater than theMinfield value.
As with single value args the destination field can be set
package main
import (
"fmt"
"log"
"os"
"context"
"github.com/urfave/cli/v3"
)
func main() {
var ivals []int
cmd := &cli.Command{
Arguments: []cli.Argument{
&cli.IntArgs{
Name: "someint",
Min: 0,
Max: -1,
Destination: &ivals,
},
},
Action: func(ctx context.Context, cmd *cli.Command) error {
fmt.Println("We got ", ivals)
return nil
},
}
if err := cmd.Run(context.Background(), os.Args); err != nil {
log.Fatal(err)
}
}
Following multi value arguments are supported
FloatArgsIntArgsInt8ArgsInt16ArgsInt32ArgsInt64ArgsStringArgsUintArgsUint8ArgsUint16ArgsUint32ArgsUint64ArgsTimestampArgs
It goes without saying that the chain of arguments set in the Arguments slice need to be consistent. Generally a glob
argument(max=-1) should be set for the argument at the end of the slice. To glob args we aren't interested in we could add
the following to the end of the Arguments slice and retrieve them as a slice
&StringArgs{
Max: -1,
},
Mixing named arguments with cmd.Args()¶
When a command declares named arguments in Arguments, each named argument consumes the positional arguments it needs
from the command line. The cmd.Args() method returns only the positional arguments that were not consumed by a
named argument. To retrieve the value of a named argument, use the cmd.{Type}Arg() function (for e.g cmd.StringArg())
as described above.
For example
package main
import (
"context"
"fmt"
"log"
"os"
"github.com/urfave/cli/v3"
)
func main() {
cmd := &cli.Command{
Arguments: []cli.Argument{
&cli.StringArg{Name: "first"},
},
Action: func(ctx context.Context, cmd *cli.Command) error {
fmt.Printf("first=%q leftover=%v", cmd.StringArg("first"), cmd.Args().Slice())
return nil
},
}
if err := cmd.Run(context.Background(), os.Args); err != nil {
log.Fatal(err)
}
}
$ greet boo bar
first="boo" leftover=[bar]
Here boo is consumed by the named StringArg and cmd.Args() contains only the leftover bar. To collect every
remaining positional argument as a slice, add a glob argument at the end of the Arguments slice and read it with the
corresponding cmd.{Type}Args() function:
&StringArgs{
Name: "rest",
Max: -1,
},
With the command above, cmd.StringArgs("rest") returns []string{"bar"} while cmd.Args() is empty.