Flag Action should be called when value is set by alternative sources.

[project0]

Checklist

• Are you running the latest v3 release? The list of releases is here.
  v3.0.0-beta1
• 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.

What problem does this solve?

Fix action beeing called for all circumstances when a value is set by either a flag or alternative source. Currently the flag action is only executed when given as argument.

example:

		Flags: []cli.Flag{
			&cli.StringFlag{
				Name:    flag_log_level,
				Usage:   "The log level (trace, debug, info, warn, error, fatal, panic)",
				Value:   "info",
				Sources: cli.EnvVars(flagEnv(flag_log_level)),
				Action: func(ctx context.Context, cmd *cli.Command, value string) error {
					log.Info("Setting log level to ", value)
					level, err := log.ParseLevel(value)
					if err != nil {
						return err
					}
					log.SetLevel(level)
					return nil
				},
			},

Solution description

When a env var is set, the action should be called.

Describe alternatives you've considered

not using in this case as it is has no consistent experience for users.

[dearchap]

@project0 Can you set Local: true for cli.StringFlag and try ?

[project0]

@dearchap indeed, setting Local true populates the value. Is this the intended behavior? If so, documenting it would be beneficial in this case.

[dearchap]

The problem is that by default we arent running FlagAction for "non local" flags. Flags which are "non local" are available to all subcommands as well and there was a discussion as to how flag actions should be run for these kinds of flags. Local means that the flag is local only to current command and will have its flag actions run. Let me think how to proceed with this.

cc @urfave/cli

[dearchap]

In this case suppose your flag is "non local" you could invoke it something like this

root cmd subcmd --log-level debug

we can run action for all flags(including log level ) for subcmd

but say you invoke it like this

LOG_LEVEL=debug root cmd subcmd

the log-level flag is set from environment when should the flag action be run ? or for example

LOG_LEVEL=debug root cmd --log-level info subcmd

It starts getting complicated.