-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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] - Implement Sub-App Labels #2695
[Merged by Bors] - Implement Sub-App Labels #2695
Conversation
d86a5b4
to
bc75882
Compare
ad5dad1
to
cf6b976
Compare
The new crate must also be added to the |
80c5c07
to
a93e204
Compare
Move the label implementation and derive code to bevy_utils and bevy_macro_utils crates to make it easier to reuse in other crates.
This replaces the temporary strategy of using indexes to access sub-apps.
I have a number of small tweaks that I'd normally just push to your branch, but it looks like you've disabled that permission. I'll just merge this as-is and follow up with another pr. |
(in the interest of time) |
bors r+ |
This is a rather simple but wide change, and it involves adding a new `bevy_app_macros` crate. Let me know if there is a better way to do any of this! --- # Objective - Allow adding and accessing sub-apps by using a label instead of an index ## Solution - Migrate the bevy label implementation and derive code to the `bevy_utils` and `bevy_macro_utils` crates and then add a new `SubAppLabel` trait to the `bevy_app` crate that is used when adding or getting a sub-app from an app.
Pull request successfully merged into pipelined-rendering. Build succeeded: |
This is a rather simple but wide change, and it involves adding a new
bevy_app_macros
crate. Let me know if there is a better way to do any of this!Objective
Solution
bevy_utils
andbevy_macro_utils
crates and then add a newSubAppLabel
trait to thebevy_app
crate that is used when adding or getting a sub-app from an app.