Strange behavior of CLI flags

[jetexe]

Checklist

• Are you running the latest v3 release? The list of releases is here.
• Did you check the manual for your release? The v3 manual is here.
• Did you perform a search about this feature? Here's the GitHub guide about searching.

Problem

Currently if you mark your flag as required and try to call a command with --help flag you will get an error:

Required flag "<name>" not set

Same for the validation: If you want to print help you will get the validation error.

Proposal

I'm suggesting we don't run a validation and required check during help printing

[dearchap]

@jetexe Unfortunately this is expected behavior. This has been an ongoing issue with urfave/cli given its architecture.

[BlackHole1]

I'm not sure if this is very difficult to achieve, but I would like to know if we can provide a switch in version v3. Something like:

&cli.StringFlag{
	Name:               "name",
	Required:           true,
	HelpExcludeRequire: false // Default: true
},

or

Name: "config",
HelpExcludeRequireFlags: true
Flags: []cli.Flag{
	&cli.StringFlag{
		Name:        "name",
		Required:    true,
	},
},

[tarampampam]

Unfortunately, I have the same problem as described 😞

[jetexe]

provide a switch

The problem is in the prepare process. cli parses flags and command first, and only after that makes a decision to print the help. I wonder if we can ignore validation and required flags errors in case of help printing

[dearchap]

Should be fixed by #1987 . @jetexe please test with latest v3 and let me know,