cobra
cobra copied to clipboard
spf13
A Commander for modern Go CLI interactions
Close #571 and Close #576. This PR is based on #841, and it must be merged after that. See difference: https://github.com/umarcor/cobra/compare/feat-matchvalid...umarcor:feat-validinhelp The added feature is to modify the output of...
Fix #838 and Fix #745. 5 of the commits in this PR are about refactoring `args_test.go`. The sixth one (`feat: generalize ValidArgs; use it implicitly with any validator`) moves the...
`-o default` supplied to `complete` forces bash to provide the default suggestions when the custom bash completion scripts do not provide any values (as is described [here](https://www.gnu.org/software/bash/manual/html_node/Programmable-Completion-Builtins.html)). This is a...
Signed-off-by: Pierre-Emmanuel Jacquier I want to solve this issue: https://github.com/spf13/cobra/issues/340 This is a good point ! I have also add a flag `ShowRunErrorUsage` to do like before !
Not all CLIs want to enforce POSIX standards Can cobra provide a way to choose between [pflag](https://github.com/spf13/pflag) vs non-POSIX flag parser?
Right now users decide on supported command name using `Command::Use` and `Command::Aliases`. There is no way to tell Cobra to use case-insensitive name matching. Cobra has `SetGlobalNormalizationFunc` which can be...
I was looking forward to this new release for the new group validators, but I have found that `MarkFlagsRequiredTogether` doesn't quite suit my needs, because it enforces that all members...
### Background Suppose you want to make a simple app that lets you migrate from database to database, and I want to allow the end user to **supply either _a...
