Nicola Papale 0294bb191d Move AppTypeRegistry to bevy_ecs (#8901) ... # Objective - Use `AppTypeRegistry` on API defined in `bevy_ecs` (https://github.com/bevyengine/bevy/pull/8895#discussion_r1234748418) A lot of the API on `Reflect` depends on a registry. When it comes to the ECS. We should use `AppTypeRegistry` in the general case. This is however impossible in `bevy_ecs`, since `AppTypeRegistry` is defined in `bevy_app`. ## Solution - Move `AppTypeRegistry` resource definition from `bevy_app` to `bevy_ecs` - Still add the resource in the `App` plugin, since bevy_ecs itself doesn't know of plugins Note that `bevy_ecs` is a dependency of `bevy_app`, so nothing revolutionary happens. ## Alternative - Define the API as a trait in `bevy_app` over `bevy_ecs`. (though this prevents us from using bevy_ecs internals) - Do not rely on `AppTypeRegistry` for the API in question, requring users to extract themselves the resource and pass it to the API methods. --- ## Changelog - Moved `AppTypeRegistry` resource definition from `bevy_app` to `bevy_ecs` ## Migration Guide - If you were **not** using a `prelude::*` to import `AppTypeRegistry`, you should update your imports: ```diff - use bevy::app::AppTypeRegistry; + use bevy::ecs::reflect::AppTypeRegistry ```		2023-06-21 17:25:01 +00:00
..
component.rs	Make function pointers of ecs Reflect* public (#8687)	2023-06-19 14:06:58 +00:00
map_entities.rs	Split the bevy_ecs reflect.rs module (#8834)	2023-06-18 23:43:10 +00:00
mod.rs	Move AppTypeRegistry to bevy_ecs (#8901)	2023-06-21 17:25:01 +00:00
resource.rs	Make function pointers of ecs Reflect* public (#8687)	2023-06-19 14:06:58 +00:00