-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
cargo add
wrongly autocorrects crates when vendored
#14309
Comments
🤦♀️ You are completely right, this is exactly the same situation/symptom. I can't check it directly, but reading through it, that seems to be the case. Sorry for the noise, I really keep forgetting what the latest version is and did not read further to see the date line. I'll close and re-check once I can. If it somehow is different, I'll reopen. NB: The reason your linked issue didn't show up in my search, was because I looked for the |
Problem
When using
cargo add
while vendored it 'autocorrects' the crate name, even for quite far string distances and for crates that are included in the vendored directory!(I also think that the distance it corrects to, is too far for such a short string. Given that adding a crate to your Cargo.toml is quite consequential wrt to access rights, having an unknown one being installed is not ideal. Especially if not vendored.)
A quick demonstration:
This confused me for a moment, when I then tried 'cargo update' it finally dawned on me that it was my vendoring of packages that caused this odd output.
Steps
cargo vendor
).cargo/
filecargo add
for a crate that existsPossible Solution(s)
No response
Notes
No response
Version
The text was updated successfully, but these errors were encountered: