Argument value should take precedence over subcommand with the same name

[axelchalon]

rustc 1.18.0 / clap 2.26.0

When using the argument value notation (as opposed to argument=value), when a top-level argument has a value with the same name as a subcommand, Clap parses this as running the subcommand and using the top-level argument with no value (even though one is required).

Sample Code / Steps to Reproduce the Issue

App::new("My program")
    .arg(Arg::from_usage("--ui-path=<PATH>"))
    .subcommand(SubCommand::with_name("signer"))
    .get_matches();

$ program --ui-path signer

error: The argument '--ui-path <PATH>' requires a value but none was supplied       

USAGE:               
    toast --ui-path <PATH> [SUBCOMMAND]   

For more information try --help                        

Thanks!

[kbknapp]

Agreed. Sorry for the delay, I've been traveling for work for the past month and a half. I'll mark this as a bug.

A workaround in the meantime is to use Arg::require_equals which requires --ui-path=signer and disallows --ui-path signer

Another workaround is to disallow subcommands when a valid arg has been found. I.e. disallow the program <arg> <subcommand> <arg> structure making it program <args> or program <subcommand> <args> but not mixing. This is done with AppSettings::ArgsNegateSubcommands