bevy_scene: Use FromReflect
on extracted resources
#15753
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
Fixes #15726
The extraction logic for components makes use of
FromReflect
to try and ensure we have a concrete type for serialization. However, we did not do the same for resources.The reason we're seeing this for the glam types is that #15174 also made a change to rely on the glam type's
Serialize
andDeserialize
impls, which I don't think should have been merged (I'll put up a PR addressing this specifically soon).Solution
Use
FromReflect
on extracted resources.Testing
You can test locally by running: