Global options for sub-commands

[IGx89]

The logging example does a great job showing how global options such as --logLevel can be implemented. When attempting to use its approach with subcommands however, it seems unnatural. For instance, this doesn't work:

myapp command arg1 subcommand --logLevel d

while this does:

myapp command arg1 --logLevel d subcommand

Is that intentional behavior, or a bug? The first example, with logLevel at the end, seems more natural to me and is how the dotnet CLI works as well (which appears to be one of your inspirations).

Thanks for making this library!

[nils-a]

Much the same as #657 - you can create global options by subclassing from a common settings class.

As to the order of commands/subcommands and options: Currently, all options and arguments need to be last. #193 addresses this issue.

[IGx89]

That's the behavior I want actually, but am not getting. Here's a repro that should hopefully explain better: https://github.com/IGx89/spectre-console-global-options-example. Run it with list arg1 package --verbosity 3 and it will print Verbosity: 0, but changing to list arg1 --verbosity 3 package will print Verbosity: 3,

[nils-a]

The difference between my and your code is config.AddBranch<ListSettings>("list", ... - my code does not use the generic overload. So when you change your code to look like config.AddBranch("list", ... you'll get the result I described above.

Now, whether this difference was intended, I'm currently not sure. Need to dig into that.

[IGx89]

That makes sense. I don't quite get the results above since it then requires me to move the location of the argument (it changes it to list package arg1 --verbosity 3), which is a deal breaker, so I'll wait for you to hopefully confirm the difference wasn't intended :)

[nils-a]

@IGx89 sorry for the late reply. This is actually intended.

If you add a branch like so config.AddBranch<BaseSettingsForBranch>("branchName") you'll need to specify the base settings after the branch name. Additionally, a branch that was created in this way can only contain commands whose Settings inherit from BaseSettingsForBranch.

At the same time, settings specific to a command must be passed after the command.

So yes, having myApp.exe branch --branchSetting value command --commandSetting value is the way things are currently. Probably until #193 has been fixed.

[IGx89]

Thanks for digging into that! I can't remember using a CLI whose command processing functioned that way, but the explanation makes sense. I've added my vote to that issue!