Strange behavior of CLI flags about cli

[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