Introduce public World::register_dynamic_bundle
method
#18198
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.
Registering dynamic bundles was not possible for the user yet.
It is alone not very useful though as there are no methods to clone, move or remove components via a
BundleId
. This could be a follow-up work if this PR is approved and such a third (besidesT: Bundle
andComponentId
(s)) API for structural operation is desired. I certainly would use a hypotheticalEntityClonerBuilder::allow_by_bundle_id
.I personally still would like this register method because I have a
Bundles
-like custom data structure and I would like to not reinvent the wheel. Then instead of having boxedComponentId
slices in my collection I could look up explicit and required components there.For reference scroll up to the typed version right above the new one.