-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Rename bevy_platform_support to bevy_platform #18813
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
Conversation
Remember the migration guide too :) |
None needed. This has not landed for users yet |
Ah but we do need to update the bevy_utils -> bevy_platform_support migration guide. Got it :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A better name, and good to do this before it's big launch day!
Should the published crate under the old name be updated in a way to express it is outdated? |
The goal of `bevy_platform_support` is to provide a set of platform agnostic APIs, alongside platform-specific functionality. This is a high traffic crate (providing things like HashMap and Instant). Especially in light of #18799, it deserves a friendlier / shorter name. Given that it hasn't had a full release yet, getting this change in before Bevy 0.16 makes sense. - Rename `bevy_platform_support` to `bevy_platform`.
Objective
The goal of
bevy_platform_support
is to provide a set of platform agnostic APIs, alongside platform-specific functionality. This is a high traffic crate (providing things like HashMap and Instant). Especially in light of #18799, it deserves a friendlier / shorter name.Given that it hasn't had a full release yet, getting this change in before Bevy 0.16 makes sense.
Solution
bevy_platform_support
tobevy_platform
.