Expose sorting methods in Children
#8522
Merged
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
order
CSS property, that declaratively re-orders flex box items by a numeric value, similar to z-index, but in space.Solution
We removed the ability to directly construct
Children
from&[Entity]
some time ago (#4197 #5532) to enforce consistent hierarchies (RFC 53). If I understand it correctly, it's currently possible to re-order children by usingChildren::swap()
orcommands.entity(id).replace_children(...)
, however these are either too cumbersome, needlessly inefficient, and/or don't take effect immediately.This PR exposes the in-place sorting methods from the
slice
primitive inChildren
, enabling imperatively sorting children in place via&mut Children
, while still preserving consistent hierarchies.Changelog
Added
slice
primitive are now exposed by theChildren
component, allowing imperatively sorting children in place (Useful for UI scenarios such as lists)