cobra

cobra copied to clipboard

Handle requiredFlags errors in the same way as errors originating from parsing flags.

6

At the moment there is a difference between the error messages + output when a required argument is not filled in compared to when an unexisting flag is passed. I...

nclaeys

Remove indentation causing RST errors

4

We generate our docs in RST from Cobra. I removed the indentations causing an error in the generated RST. This also makes the long descriptions consistent with the other completion...

melissamahoney-mongodb

Upgrade gopkg.in/yaml.v2 to gopkg.in/yaml.v3

5

Upgrade the yaml dep to version 3.

inteon

feat: make InitDefaultCompletionCmd public

10

closes #1464 I also took the liberty to directly call it when generating docs as it seems that was already the case for `InitDefaultHelpCmd`

gssbzn

feat(completion): add default completion hidden if there are no subcmds

8

This is an alternate/superseding implementation for #1392. The default completion is useful also in cases where there are no subcommands, for example to provide completion for flags, and custom completions...

scop

feat(completion): add option to create default command alone

9

The current implementation of the default completion (and help) commands makes them available only when there are some other commands defined. This rules them out for apps that have no...

scop

command: Allow overriding of flag parse function

4

To allow setting a user-defined flag parser, we add a new SetFlagParseFunc to Command. This function, when set, will be called instead of pflag.Parse.

vkareh

Check if command already exists before attempting to create

3

These changes makes sure a command doesn't exist before attempting to create it, if it does the user gets a `command already exists` message. I lost a lot of uncommited...

kodejuice

Check for disable auto gen tag on parents commands before filling man…

5

… headers

dmartin35

Adds Persistent{Pre,Post}Run hook chaining

10

PersistentPreRun and PersistentPostRun are chained together so that each child PersistentPreRun is ran, and the PersistentPostRun are ran in reverse order. For example: Commands: root -> subcommand-a -> subcommand-b root...

poy