Hi, I was wondering if there was a way to get a list of flags for a particular command that has been defined using cmd.Flags().StringVarP(&file, "file", "f", fileDefault, "Source file") I've gone through the docs but was not able to find any function for this. For now, I'm able to get a list of...

It would seem useful if setting Args: cobra.NoArgs implied that no arg completions would be generated by default. Currently I believe this requires also setting ValidArgsFunction: cobra.NoFileCompletions.

I need to convert the Cobra errors about failure to parse a flag to my own messages. The messages are dependent on which flag failed to be parsed. The error passed to the function has no type from which to pull that information, and the function doesn't take any parameters that indicate which flag c...

We rely on PersistentPreRunE to setup some scaffolding to be used later in the command pipeline. When doing this, calling command --help appears to bypass that function altogether. I can't find if this is expected behavior, or a bug. Ideally these Persistent/PreRun functions would always run as docu...

What is status of Workspace with cobra-init?

Hey everyone, quick question is it possible to check if default help command was invoked? Normally I would call command.helpCommand.CalledAs() == "" but unfortunately helpCommand is not exported. Just to be clear I don't want to override default helper command and I know that I can call Commands(...

I have run go install github.com/spf13/[email protected] but cobra still not recognized on terminal. How can I resolve this?

When adding a Slice type parameter binding in the flag with the following command: cmd.Flags().StringSliceVar(&actions, "actions", []string{}, "actions") If the actions value is not passed as a parameter during execution, the value obtained through cmd.Flag("actions").Value.String() will be "[]"...

When using the option NoOptDefVal for flags to enable users to use a flag both as a switch and as a configuration, if the user provides the flag and value in the format --flag=value or -f=value NoOptDefVal works as expected, however when using a space to separate the flag and value the value is trea...

It would be nice if I could get completions for file paths because of programs like glow.exe which require it. It appears based on this code that it is by design? I would expect default completion to a file path. cobra/powershell_completions.go Lines 200 to 211...