Charles Bournhonesque afff818e5c Update the Children component of the parent entity when a scene gets deleted (#12710) ... # Objective - A scene usually gets created using the `SceneBundle` or `DynamicSceneBundle`. This means that the scene's entities get added as children of the root entity (the entity on which the `SceneBundle` gets added) - When the scene gets deleted using the `SceneSpawner`, the scene's entities are deleted, but the `Children` component of the root entity doesn't get updated. This means that the hierarchy becomes unsound, with Children linking to non-existing components. ## Solution - Update the `despawn_sync` logic to also update the `Children` from any parents of the scene, if there are any - Adds a test where a Scene gets despawned and checks for dangling Children references on the parent. The test fails on `main` but works here. ## Alternative implementations - One option could be to add a `parent: Option<Entity>` on the [InstanceInfo](df15cd7dcc/crates/bevy_scene/src/scene_spawner.rs (L27)) struct that tracks if the SceneInstance was added as a child of a root entity		2024-03-29 13:13:32 +00:00
..
src	Update the Children component of the parent entity when a scene gets deleted (#12710)	2024-03-29 13:13:32 +00:00
Cargo.toml	Make feature(doc_auto_cfg) work (#12642)	2024-03-23 02:22:52 +00:00