Expose access to SubApps
within App
#16952
Merged
+10
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Objective
SubApps
is visible within the documentation forbevy_app
. However, no way of accessing theSubApps
field inApp
is currently available.Solution
Expose two new functions,
App::sub_apps()
andApp::sub_apps_mut()
, which give immutable and mutable access toSubApps
respectively.The other solution is to hide
SubApps
, which I submitted as a PR at #16953.Testing
Because of the simplicity of the changes, I only tested by compiling
bevy_app
- which compiled successfully.Note:
SubApps
, and its corresponding field onApp
, are not used outside ofbevy_app
- which means that compiling the other crates is not necessary.