Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no suggestion for possible value when using 'long=' format #192

Closed
kbknapp opened this issue Aug 27, 2015 · 0 comments
Closed

no suggestion for possible value when using 'long=' format #192

kbknapp opened this issue Aug 27, 2015 · 0 comments
Labels
A-parsing Area: Parser's logic and needs it changed somehow. C-bug Category: Updating dependencies

Comments

@kbknapp
Copy link
Member

kbknapp commented Aug 27, 2015

When setting up a long option with possible values, and you run --long=value if value isn't valid you will not get an error. Yet running --long value will result in the appropriate error.

Example test:

static VALUES: [&'static str; 2] = ["possible", "vals"];

fn main() {
    App::new("test").arg(Arg::from_usage("--option <val> 'some option'").possible_values(&VALUES)).get_matches();
}
@kbknapp kbknapp added C-bug Category: Updating dependencies P1: urgent A-parsing Area: Parser's logic and needs it changed somehow. labels Aug 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-parsing Area: Parser's logic and needs it changed somehow. C-bug Category: Updating dependencies
Projects
None yet
Development

No branches or pull requests

1 participant