Show usage description when using help for option commands as well

[kdawgwilk]

It would be nice if prompting for the usage description was consistent for different types of commands. In some places you can type cmd help and other times you have to type cmd subCommand -h. It isn't consistent and can confuse the user IMO.

[jakeheis]

Could you explain what you mean by this a little bit more? I'm not sure I totally understand what you're saying

[kdawgwilk]

It would be better if -h and help were interchangeable but it doesn't appear to be this way.

e.g.

Attempting to use help on a subcommand is not an acceptable way to show the usage description.

[jakeheis]

While I agree it would be nice to make this more consistent, a change like this would make it impossible to pass 'help' as an argument to a function. For example, if you were implementing a CLI like git and had a file named 'help', you would be unable to run mygit add help. Since this feature would interfere with the workings of commands, I think it's best to not implement it.

[kdawgwilk]

I am fine with not using help but at least allow -h to be used everywhere.

[jakeheis]

-h should work everywhere:

public protocol OptionCommand: Command {
    
     ...

    /// Whether help for the command should be shown when -h is passed. Default is true.
    var helpOnHFlag: Bool { get }

    ...

}

If -h isn't working for your commands, then that's a bug that I would love to fix!