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

Changelog for optional vectors may have wrong example for old behaviour #249

Closed
AluisioASG opened this issue Sep 2, 2019 · 1 comment · Fixed by #250
Closed

Changelog for optional vectors may have wrong example for old behaviour #249

AluisioASG opened this issue Sep 2, 2019 · 1 comment · Fixed by #250

Comments

@AluisioASG
Copy link

From the changelog; issue in comments:

If you need to fall back to the old behavior you can use a type alias:

type Something = Vec<String>; // Not actually used
#[derive(StructOpt)]
struct Opt {
  #[structopt(long)]
  fruit: Option<Vec<String>>, // Shouldn't this be `Option<Something>`?
}
@CreepySkeleton
Copy link
Collaborator

That's right, thanks for reporting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants