Incorrect render structure in Navigation PageContext

Good catch. The child component was positioned as a render child:

[
    '#type' => 'component',
    '#component' => 'navigation:title',
    0 =>  [
      '#type' => 'component',
      '#component' => 'navigation:title',
   ]
]

Inside of side by side:

[
    '#type' => 'component',
    '#component' => 'navigation:title',
],
[
    '#type' => 'component',
    '#component' => 'navigation:title',
]

I'm not sure this is the place for it, but is there somewhere we can make this more robust to prevent this issue in the future?

I'm not sure this is the place for it, but is there somewhere we can make this more robust to prevent this issue in the future?

In https://www.drupal.org/project/drupal/issues/3494634#comment-16074642 📌 Compatibility between SDC and the Form API Active I am asking

Is it the opportunity to deprecate #slots and to promote render children as the expected way of settings slots in SDC ?

This may make this more robust, because a numeric slot will be caught as invalid.

That might be the long term fix, I meant something more short term, like throwing an error if numeric keys are found.

That might be the long term fix, I meant something more short term, like throwing an error if numeric keys are found.

Interesting. I have created a dedicated issue: 📌 What do we do with numeric render children keys? Active

The long term fix would be in \Drupal\Core\Render\Element::children - we already check for int there, so we could introduce a deprecation error in 11.x and start throwing an exception in 12

Committed to 11.x - thanks

larowlan → closed merge request !11894