| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2024-06-30 | Fix testable example output comment formatting | Hugo Hromic | |
| 2024-06-27 | Fix crash on errors in package-level `MustParse` | Hugo Hromic | |
| 2023-06-03 | fixed tests | Pablo Diaz | |
| 2023-06-03 | added tests and fixed usage | Pablo Diaz | |
| 2023-06-03 | ignores short and long parameters | Pablo Diaz | |
| 2023-02-08 | clean up customizable stdout, stderr, and exit in parser config | Alex Flint | |
| 2022-02-09 | fix bracketing for non-required positionals | Alex Flint | |
| 2021-09-18 | Merge remote-tracking branch 'origin/master' into usage-for-subcommands | Alex Flint | |
| 2021-08-20 | bump go-scalar to v1.1 and add documentation about supported types | Alex Flint | |
| 2021-05-09 | add FailSubcommand, WriteUsageForSubcommand, WriteHelpForSubcommand | Alex Flint | |
| 2021-04-20 | fix the mappings-with-commas example | Alex Flint | |
| 2021-04-19 | updated the example for mappings with commas | Alex Flint | |
| 2021-04-19 | test coverage 100% !! | Alex Flint | |
| 2021-04-19 | add an runnable example for mappings | Alex Flint | |
| 2020-08-06 | add documentation and examples showing how to override the short and long ↵ | Alex Flint | |
| option names together | |||
| 2020-01-25 | Print global options in help for subcommands | Dylan Allbee | |
| fixes #101 | |||
| 2020-01-19 | usage: if the program supports subcommands, mention it | Marco Molteni | |
| 2019-11-30 | Final improvements | Andrew Morozko | |
| 2019-11-30 | Various changes | Andrew Morozko | |
| 2019-11-29 | Added the "dataname" tag | Andrew Morozko | |
| 2019-10-21 | update documentation to new way of specifying defaults | Alex Flint | |
| 2019-08-06 | add subcommands to readme | Alex Flint | |
| 2019-05-03 | print help and usage at subcommand level if necessary | Alex Flint | |
| 2019-05-03 | add subcommands to usage string | Alex Flint | |
| 2019-05-03 | add expected output for usage example | Alex Flint | |
| 2019-05-03 | add expected outputs to all examples | Alex Flint | |
| 2017-03-04 | Adding separate tag option | Kenneth Shaw | |
| As outlined in #49, there is a need to mimic the behavior of other applications by interweaving positional and non-positional parameters. This change adds the 'separate' option that will force a arg of type []string to only read the next supplied value. For example, when dealing with the following arg type: var MyArgs struct { Pos []string `arg:"positional"` Separate []string `arg:"-s,separate"` } This commit will parse the following command line: ./app pos1 pos2 -s=separate1 -s=separate2 pos3 -s=separate3 pos4 Such that MyArgs.Pos will be [pos1 pos2 pos3 pos4] and MyArgs.Separate will be [separate1 separate2 separate3]. Unit tests for the above have also been written and are included in this commit, as well as the addition of a section to README.md and an example func in example_test.go. Fixes #49 | |||
| 2016-07-31 | fix example function names | Alex Flint | |
| 2015-11-01 | fix examples | Alex Flint | |
| 2015-11-01 | add .travis.yml | Alex Flint | |
| 2015-11-01 | added runnable examples | Alex Flint | |
 |
index : jcarr/go-arg | |
| Unnamed repository; edit this file 'description' to name the repository. |
| summaryrefslogtreecommitdiff |
path: root/example_test.go