2015-11-01 13:34:22 -06:00
[![GoDoc ](https://godoc.org/github.com/alexflint/go-arg?status.svg )](https://godoc.org/github.com/alexflint/go-arg)
2015-11-01 15:40:27 -06:00
[![Build Status ](https://travis-ci.org/alexflint/go-arg.svg?branch=master )](https://travis-ci.org/alexflint/go-arg)
2015-11-01 13:34:22 -06:00
2015-10-31 21:10:13 -05:00
## Structured argument parsing for Go
2015-10-31 20:46:56 -05:00
2015-11-01 13:34:22 -06:00
Declare the command line arguments your program accepts by defining a struct.
2015-10-31 20:49:20 -05:00
```go
2015-10-31 20:46:56 -05:00
var args struct {
2015-10-31 20:51:21 -05:00
Foo string
Bar bool
2015-10-31 20:46:56 -05:00
}
arg.MustParse(& args)
2015-10-31 20:49:20 -05:00
fmt.Println(args.Foo, args.Bar)
2015-10-31 20:46:56 -05:00
```
2015-10-31 20:49:20 -05:00
```shell
2015-10-31 20:46:56 -05:00
$ ./example --foo=hello --bar
2015-10-31 21:10:13 -05:00
hello true
2015-10-31 20:46:56 -05:00
```
2015-10-31 21:15:43 -05:00
### Required arguments
2015-10-31 20:46:56 -05:00
2015-10-31 20:49:20 -05:00
```go
2015-10-31 20:46:56 -05:00
var args struct {
Foo string `arg:"required"`
Bar bool
}
arg.MustParse(& args)
```
2015-11-01 15:53:51 -06:00
```shell
$ ./example
usage: example --foo FOO [--bar]
error: --foo is required
```
2015-10-31 21:15:43 -05:00
### Positional arguments
2015-10-31 20:46:56 -05:00
2015-10-31 20:49:20 -05:00
```go
2015-10-31 20:46:56 -05:00
var args struct {
Input string `arg:"positional"`
Output []string `arg:"positional"`
}
arg.MustParse(& args)
2015-11-01 13:34:22 -06:00
fmt.Println("Input:", args.Input)
fmt.Println("Output:", args.Output)
2015-10-31 20:46:56 -05:00
```
```
$ ./example src.txt x.out y.out z.out
Input: src.txt
Output: [x.out y.out z.out]
```
2015-10-31 20:48:38 -05:00
### Usage strings
2015-10-31 20:51:21 -05:00
```go
var args struct {
Input string `arg:"positional"`
Output []string `arg:"positional"`
Verbose bool `arg:"-v,help:verbosity level"`
Dataset string `arg:"help:dataset to use"`
Optimize int `arg:"-O,help:optimization level"`
}
arg.MustParse(& args)
```
2015-10-31 20:49:20 -05:00
```shell
2015-10-31 20:46:56 -05:00
$ ./example -h
usage: [--verbose] [--dataset DATASET] [--optimize OPTIMIZE] [--help] INPUT [OUTPUT [OUTPUT ...]]
positional arguments:
input
output
options:
2015-11-01 15:53:51 -06:00
--verbose, -v verbosity level
--dataset DATASET dataset to use
--optimize OPTIMIZE, -O OPTIMIZE
optimization level
--help, -h print this help message
```
### Default values
```go
var args struct {
Foo string
Bar bool
}
args.Foo = "default value"
arg.MustParse(& args)
2015-10-31 20:46:56 -05:00
```
2015-10-31 21:15:43 -05:00
### Arguments with multiple values
2015-10-31 20:51:21 -05:00
```go
2015-10-31 20:46:56 -05:00
var args struct {
Database string
IDs []int64
}
arg.MustParse(& args)
fmt.Printf("Fetching the following IDs from %s: %q", args.Database, args.IDs)
```
2015-10-31 20:49:20 -05:00
```shell
2015-10-31 20:46:56 -05:00
./example -database foo -ids 1 2 3
Fetching the following IDs from foo: [1 2 3]
```
2015-10-31 21:10:13 -05:00
2015-10-31 21:15:08 -05:00
### Installation
```shell
go get github.com/alexflint/go-arg
```
2015-11-01 13:34:22 -06:00
### Documentation
https://godoc.org/github.com/alexflint/go-arg
2015-10-31 21:10:13 -05:00
### Rationale
2015-10-31 21:13:48 -05:00
There are many command line argument parsing libraries for Go, including one in the standard library, so why build another?
2015-10-31 21:10:13 -05:00
2015-11-03 10:15:45 -06:00
The shortcomings of the `flag` library that ships in the standard library are well known. Positional arguments must preceed options, so `./prog x --foo=1` does what you expect but `./prog --foo=1 x` does not. Arguments cannot have both long (`--foo`) and short (`-f`) forms.
2015-10-31 21:10:13 -05:00
2015-10-31 21:13:48 -05:00
Many third-party argument parsing libraries are geared for writing sophisticated command line interfaces. The excellent `codegangsta/cli` is perfect for working with multiple sub-commands and nested flags, but is probably overkill for a simple script with a handful of flags.
2015-10-31 21:10:13 -05:00
2015-10-31 21:13:48 -05:00
The main idea behind `go-arg` is that Go already has an excellent way to describe data structures using Go structs, so there is no need to develop more levels of abstraction on top of this. Instead of one API to specify which arguments your program accepts, and then another API to get the values of those arguments, why not replace both with a single struct?