kingpin
getoptions
| kingpin | getoptions | |
|---|---|---|
| 2 | 7 | |
| 3,446 | 367 | |
| - | - | |
| 5.2 | 0.0 | |
| about 1 month ago | 5 months ago | |
| Go | Shell | |
| MIT License | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kingpin
-
climate "CLI Mate": a CLI library that autogenerates CLIs from structs / functions with support for nested subcommands, global / local flags, help generation from godocs, typo suggestions, shell completion and more
Args could also have detailed help (like flags) -- usage line is already auto-generated from arg(s) name and type but that's about it. This is something Cobra doesn't do for whatever reason (but https://github.com/alecthomas/kingpin does and I like it)
- What is the best way to handle flags?
getoptions
-
Is there a recommended alternative to getopts?
I like to use https://github.com/ko1nksm/getoptions
- jetopt: a dead simple wrapper around getopt you always dreamed of!
- What is the best way to handle flags?
- Adding options to scripts
-
The easiest way to parse arguments using getoptions for bash and shell scripts
A lot of people have been looking for a best practice to use getopt and getopts for long years. A number of methods to parse arguments were thought up, but no perfect solution was found. However, with the advent of the getoptions, that long journey comes to an end.
-
What is the best practice for handling parameters and flags in a bash script?
Why not use a library instead of implementing it yourself? I wrote getoptions (not getopt or getopts) which many option syntaxes can be easily supported. A lot of options are no longer an obstacle, and there is no need to use another inappropriate language for such a trivial reasons.
- [POSIX] How to Implement --args and How Should Usage Be Formatted
What are some alternatives?
cobra - A Commander for modern Go CLI interactions
shellspec - A full-featured BDD unit testing framework for bash, ksh, zsh, dash and all POSIX shells
go-flags - go command line option parser
argbash - Bash argument parsing code generator
urfave/cli - A simple, fast, and fun package for building command line apps in Go
shflags - shFlags is a port of the Google gflags library for Unix shell.
kong - Kong is a command-line parser for Go
jetopt - Friendly options formatter for getopt
pflag - Drop-in replacement for Go's flag package, implementing POSIX/GNU-style --flags.
bash-argsparse - An high level argument parsing library for bash
cli - CLI - A package for building command line app with go
bashew - bash script micro-framework - from small stand-alone script to complex projects with CI/CD and testing