[Question] Handling global options in CLI apps with v5 framework

[rozumak]

It's common for CLI apps to have global/common options that apply to most commands. These options are usually placed before the command text.

For example, in Entity Framework:

dotnet ef [options] [command]

Global options:
  --no-color       Don't colorize output.
  --prefix-output  Prefix output with level.

What is your recommendation for handling these cases using your v5 framework? Is there any support or plans to support this?

Thanks for the great framework!

[neuecc]

That's a good suggestion, I'd like to consider adding it.

[github-actions]

This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 30 days.

[jamesfoster]

@neuecc Looks like this issue has been raised several times but auto-closed due to inactivity. Any chance you could look at porting @riddlemd 's PR to the latest version? #100

I realise that implementation may not be sufficient or applicable in the latest version. I would ask, if there's a global parameter --quite , for example, do I access that through a property base.Quite, or do I need a bool quiet parameter on all my commands? Thinking about something like --nologo it would be cool to have something that runs before all commands.

public abstract class BaseCommand
{
    /// <param name="nologo">Hide the logo</param>
    public void Before(bool nologo) // somehow register this to run before ALL commands
    {
        if (!nologo) PrintLogo();
    }
}

Thanks.

[ptr727]

Following:
I'm looking at this as replacement for deprecation announced System.CommandLine.NamingConventionBinder, was looking to see how easy it would be to switch, and it seems that a couple things will be difficult, 1) no deterministic way to define an option as optional and have a default value (nullable is not an option), and 2) no obvious way to get access to global options in sub-commands.