-v flag conflict between additional commands and default command

[BCoskun]

Information

• V0.47 and 0.48 behavior change for -v flag.

Describe the bug
I was using -v short hand flag for sub command and it was working until V0.48 . With Version 0.48 parsing behavior changed and when we use -v for subcommand, it print application version directly.

To Reproduce
With Version 0.47 ConsoleApp.exe -v and ConsoleApp.exe subcommand -v has different behavior.
With Version 0.48 ConsoleApp.exe -v and ConsoleApp.exe subcommand -v has same behavior.

Expected behavior
The sub command -v should be parsed for the sub command context

---

Please upvote 👍 this issue if you are interested in it.

[JKamsker]

Can you provide an unit test for this?
This would help understanding the problem and having a definition of "done"

Similar bug in the past #1400
My issue probably caused this change 😅

I guess there is no absolute right answer, and if it is it is harder to do than it may first look like

[FrankRay78]

I introduced the bug @JKamsker, unfortunately. I knew it was a breaking change, and flagged it as such, but I think the change in functionality is probably now best described as a regression. I'll add this to my stack to review/address.

#1400 (comment)

And

FYI. I've submitted the PR above to revert this to existing behaviour @JKamsker

#1400 (comment)

Background
Apologies for creating this problem. The above issue description is exactly correct, we changed this behaviour between 0.47 and 0.48.

It had worked as per the current 0.48 earlier than 0.47, then I did some refactoring, changed it to the behaviour in 0.47, flagged it as a breaking change (thinking it was fine to make breaking changes, if warranted, as we are still < version 1.0), which was accepted by the maintainer team and merged.

Then we found a number of unhappy users of spectre.console (because we broke their apps), and so on further consideration, we reverted the change. Unfortunately, I doubt we'd be looking to revert it once again.

[FrankRay78]

This appears fixed in 0.49.1 @BCoskun

I've created the following console application to test the behaviour:

using Spectre.Console;
using Spectre.Console.Cli;
using System.ComponentModel;

public class HelloCommandSettings : CommandSettings
{
    [CommandOption("-v|--version")]
    [DefaultValue("Hello world")]
    public string Message { get; set; }
}

public class HelloCommand : Command<HelloCommandSettings>
{
    public override int Execute(CommandContext context, HelloCommandSettings settings)
    {
        AnsiConsole.MarkupLine(settings.Message);
        return 0;
    }
}

public static class Program
{
    public static int Main(string[] args)
    {
        var app = new CommandApp();

        app.Configure(config =>
        {
            config.AddCommand<HelloCommand>("hello");
        });

        return app.Run(args);
    }

Behaviour under different spectre.console versions

0.47

0.48

0.49.1

[FrankRay78]

There is still a bug, however, as when I add in the application version using the following configuration line:

            config.SetApplicationVersion("1.0");

The help text for the hello command erroneously includes the -v, --version associated at the application root:

At least the application behaviour is now functioning correctly.