Remove the Component
trait implementation from Handle
#15796
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
Component
trait impl fromHandle<T>
#15716Handle<MeshletMesh>
as a component #15718Solution
Handle<MeshletMesh>
with a newMeshletMesh3d
componentSpriteBundle
still had aHandle<Image>
field. I've removed this.bevy_sprite
incorrectly added aHandle<Image>
field outside of theSprite
component.Handle
s, switched those to their corresponding wrappers.Handle<Image>
were changed to querySprite
Testing
Migration Guide
Handle
can no longer be used as aComponent
. All existing Bevy types using this pattern have been wrapped in their own semantically meaningful type. You should do the same for any customHandle
components your project needs.The
Handle<MeshletMesh>
component is nowMeshletMesh3d
.The
WithMeshletMesh
type alias has been removed. UseWith<MeshletMesh3d>
instead.