-
Notifications
You must be signed in to change notification settings - Fork 12
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
Detect duplicate bevy dependencies #15
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Just as a note, I edited Jan's original message as part of my issue-pass in #34. |
Note that the compiler errors generated in these cases might get improved soon, then we might not need this lint anymore. |
Wonderful! @estebank is this something that can hit stable by November1? If so, I'll just close out this issue as not planned. (Also I know you said you're offline for 3 weeks, so no worries about responding immediately!) Footnotes
|
This can be done relatively easily with |
An issue that many beginners have when using Bevy is having duplicates of it within the dependencies. This usually happens when a user adds 3rd party crates that don't support the same major versions, such as one depending on Bevy 0.14 and the other depending on Bevy 0.13.
When this happens, users will get difficult error messages about type incompatibilities and conflicting versions, which can be really confusing! We should make a custom lint that specifically detects this in
Cargo.lock
and emits a clear error message on what happened and how to fix it.The text was updated successfully, but these errors were encountered: