make various entity wrapper type modules public #18248
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
Part of the #16547 series.
The entity wrapper types often have some associated types an aliases with them that cannot be re-exported into an outer module together.
Some helper types are best used with part of their path:
bevy::ecs::entity::index_set::Slice
asindex_set::Slice
.This has already been done for
entity::hash_set
andentity::hash_map
.Solution
Publicize the
index_set
,index_map
,unique_vec
,unique_slice
, andunique_array
modules.Migration Guide
Any mention or import of types in the affected modules have to add the respective module name to the import path.
F.e.:
bevy::ecs::entity::EntityIndexSet
->bevy::ecs::entity::index_set::EntityIndexSet