-
Notifications
You must be signed in to change notification settings - Fork 152
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
Unnecessary name sanitisation #265
Comments
It seems like influence of |
That's a feature, but you can use #[structopt(rename_all = "verbatim")] to manage the names by hand. |
@TeXitoi That's right, but I never thought that dots |
Err, wait, there's no way to start a name with a colon except for explicit |
From heck docs
Well, it looks like |
I am explicitely setting name with name=":somevalue", that doesn't work. This behavior was surprising though, especially that using clap directly doesn't do that. |
I think we should not change the name if it is setted explicitly, but it's technically a breaking change. |
Technically - yes, it is, but I highly doubt that many users has been relying on this behavior. We should really ask on |
@TeXitoi I think this is basically a bug, and semver states that bugfixes does not require major version bump. I'd like to conduct a survay on users.rust-lang.org, do you mind? |
I'm OK with doing it even without asking, but feel free to ask if you prefer to be sure. |
@TeXitoi this is closed too |
Clap has no problem with subcommand names starting with colon.
I need this to namespace them (users will be able to create their own, so I want standard ones not to clash witht them.
However something in structopt removes them (and anything that's not a letter) from beginning and end of subcommand name. This seems accidental.
The text was updated successfully, but these errors were encountered: