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

Publishing a crate is case-sensitive #6043

Closed
jasonwilliams opened this issue Sep 17, 2018 · 2 comments
Closed

Publishing a crate is case-sensitive #6043

jasonwilliams opened this issue Sep 17, 2018 · 2 comments
Labels
A-diagnostics Area: Error and warning messages generated by Cargo itself. C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`

Comments

@jasonwilliams
Copy link
Member

jasonwilliams commented Sep 17, 2018

It's the first time i published a crate, so i followed https://doc.rust-lang.org/book/2018-edition/ch14-02-publishing-to-crates-io.html

It didn't mention that the name of your crate is case sensitive.
I ended up publishing Boa instead of boa and I didn't realised i made the mistake until it was too late. It was only until after i published i noticed that most crates were lowercase.

Is there something we can do about this?

@alexcrichton alexcrichton added the C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` label Sep 17, 2018
@joshtriplett
Copy link
Member

By convention, we almost always use lowercase for crate names, so we should probably warn about this at some step in the process.

@epage
Copy link
Contributor

epage commented Oct 24, 2023

Considering users should have gotten a warning from rustc

warning: crate `UPPERcase_name` should have a snake case name such as `uppercase_name`, #[warn(non_snake_case)] on by default

And we now have a warning from cargo new in #12766, I'm going to close this as resolved. If there is a reason we should re-open this, let us know!

@epage epage closed this as not planned Won't fix, can't repro, duplicate, stale Oct 24, 2023
@epage epage added the A-diagnostics Area: Error and warning messages generated by Cargo itself. label Nov 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Error and warning messages generated by Cargo itself. C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants