Gino Valente 19fc1f1ed2 bevy_reflect: Fix DynamicScene not respecting component registrations during serialization (#6288) ... # Objective When running the scene example, you might notice we end up printing out the following: ```ron // ... { "scene::ComponentB": ( value: "hello", _time_since_startup: ( secs: 0, nanos: 0, ), ), }, // ... ``` We should not be printing out `_time_since_startup` as the field is marked with `#[reflect(skip_serializing)]`: ```rust #[derive(Component, Reflect)] #[reflect(Component)] struct ComponentB { pub value: String, #[reflect(skip_serializing)] pub _time_since_startup: Duration, } ``` This is because when we create the `DynamicScene`, we end up calling `Reflect::clone_value`: 82126697ee/crates/bevy_scene/src/dynamic_scene_builder.rs (L114-L114) This results in non-Value types being cloned into Dynamic types, which means the `TypeId` returned from `reflected_value.type_id()` is not the same as the original component's. And this meant we were not able to locate the correct `TypeRegistration`. ## Solution Use `TypeInfo::type_id()` instead of calling `Any::type_id()` on the value directly. --- ## Changelog * Fix a bug introduced in `0.9.0-dev` where scenes disregarded component's type registrations		2022-10-24 14:53:12 +00:00
..
de.rs	bevy_reflect: Improve serialization format even more (#5723)	2022-09-20 19:38:18 +00:00
mod.rs	bevy_reflect: Improve serialization format even more (#5723)	2022-09-20 19:38:18 +00:00
ser.rs	bevy_reflect: Fix DynamicScene not respecting component registrations during serialization (#6288)	2022-10-24 14:53:12 +00:00
type_data.rs	bevy_reflect: Improve serialization format even more (#5723)	2022-09-20 19:38:18 +00:00