-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Remove re-exports of cosmic_text types #19516
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
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.
please rely on them directly from
cosmic_text
, being sure that the version number you are using matches the version used by your version ofbevy_text
.
Standard practice – which we are currently following, see the self
in the import – would be to reëxport cosmic_text
as bevy_text::cosmic_text
to avoid this problem.
Indeed, but I think the cure is worse than the disease here, and the others in the linked thread agree. |
# Objective As discussed in bevyengine#19285, we do a poor job at keeping the namespace tidy and free of duplicates / user-conflicting names in places. `cosmic_text` re-exports were the worst offender. ## Solution Remove the re-exports completely. While the type aliases were quite thoughtful, they weren't used in any of our code / API.
Objective
As discussed in #19285, we do a poor job at keeping the namespace tidy and free of duplicates / user-conflicting names in places.
cosmic_text
re-exports were the worst offender.Solution
Remove the re-exports completely. While the type aliases were quite thoughtful, they weren't used in any of our code / API.