Ensure predictable config export order of config-defined component trees

This would be the next big DX boost after 📌 Stop storing JSON blobs in XB config entities: improve DX Active ! 😊

We have to be wary here because order is important.

With content entity versions of these trees, there is a delta field that keeps track of the order.

Here there is not, and perhaps we should introduce it.

The delta keeps track of what order sibling components (those with the same parent/slot) appear in.

Here there is not, and perhaps we should introduce it.

Here it is indeed the sequence order (which implicitly has "deltas" as keys: a PHP "list" array, so 0, 1 etc.) that ensures the correct ordering.

I'm contemplating whether this should be a beta blocker or not. It feels like it'd be safer to make this a beta blocker. Do you agree?

It feels like it should be simple enough - the main impacts here are on page regions and patterns. Add content templates if that ends up being in beta.

Tagging as such

As beta blocker tag is added, I am removing stable blocker tag

🏗️ picking this up

This should be ready for review 🤞

Per @larowlan at 📌 [SPIKE] Prove that it's possible to apply block settings update paths to stored XB component trees Active , this MR blocks that one.

Automatically closed - issue fixed for 2 weeks with no activity.