-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
[Merged by Bors] - Cherry pick "bevy_reflect: Register missing reflected types for bevy_render
(#6725)"
#6811
Conversation
…yengine#6725) Many types in `bevy_render` implemented `Reflect` but were not registered. Register all types in `bevy_render` that impl `Reflect`. This also registers additional dependent types (i.e. field types). > Note: Adding these dependent types would not be needed using something like bevyengine#5781 😉 --- - Register missing `bevy_render` types in the `TypeRegistry`: - `camera::RenderTarget` - `globals::GlobalsUniform` - `texture::Image` - `view::ComputedVisibility` - `view::Visibility` - `view::VisibleEntities` - Register additional dependent types: - `view::ComputedVisibilityFlags` - `Vec<Entity>`
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.
Looks good!
For others' reference, the only difference from #6725 is that this one doesn't have ComputedVisibilityFlags
Lets see if this merges as-is or if we need to cherry pick the CI fixes :) |
bors r+ |
FYI you shouldn't need the miri one as it hasn't been a part of r+'s for awhile |
Build failed: |
Should be fixed now after cherry picking the relevant CI fixes into the 0.9.1 branch. |
bors r+ |
bevy_render
(#6725)"bevy_render
(#6725)"
This had merge conflicts with the 0.9.1 release branch, so this had to be merged manually. Creating a PR for visibility + a final review.