Empty layout sections get rendered

This seems like a symptom (or duplicate) of #953034: [meta] Themes improperly check renderable arrays when determining visibility

The render filter is a good temporary solution.
Here's one possible long-term fix.

Rebased and switched to using an MR

Adding a patch for the 10.1.x branch.

Fixed a couple more tests

Thank you for this! See this often with clients who aren’t great with layout builder.

Still seem to be some test failures however. Definitely keeping this on the radar

@tim.plunkett added a condition so the sections do build in layout builder side.

Thoughts?

Thanks. Also seemed to cause some additional test failures that I'll look at.

So this additional checks seems to be the best way to cover all scenarios.

When adding a section _layout_builder isn't there.

Tried _admin_route but that caused test failures also.

Fixing merge (using rebase) to allow me to review better

@tim.plunkett wonder if you had a chance to review?

I'll have to re-review, the change to checking for `layout_builder_tempstore` is tricky

Tried this out on a local project and I use drush search-api-index

But I get this error

> [error] Error while trying to render item entity:node/48:en with view mode full for search index tetra_tech: Call to a member function getOption() on null in Drupal\Core\Layout\LayoutDefault->build() (line 70 of /var/www/html/webroot/core/lib/Drupal/Core/Layout/LayoutDefault.php).

So seems all scenarios aren't caught.

Adding a patch for the 10.2.x branch

Rerolled the patch for the 10.3.1 branch

I get same error for media on solr indexing:
[error] Error while trying to render item entity:media/XX:en with view mode search_index for search index INDEX-ABC: Call to a member function getOption() on null in Drupal\Core\Layout\LayoutDefault->build() (line 70 of web/core/lib/Drupal/Core/Layout/LayoutDefault.php).

Sorry for the noise, tool a random issue to check something. Please ignore.

I encountered the same issue described in #29 when applying the patch from #28. The problem occurs because \Drupal::routeMatch()->getRouteObject() returns null in non-route contexts (e.g., during Search API indexing via cron), which leads to a fatal error when getOption() is called.

To fix this, I updated the patch to use the null-safe operator, ensuring the code does not break when the route object is unavailable:

$temp_store = FALSE;
if (!empty(\Drupal::routeMatch()?->getRouteObject()?->getOption('parameters')) &&
    isset(\Drupal::routeMatch()?->getRouteObject()?->getOption('parameters')['section_storage'])) {
  $temp_store = \Drupal::routeMatch()->getRouteObject()->getOption('parameters')['section_storage']['layout_builder_tempstore'];
}

This change ensures compatibility with CLI and cron environments. I've also attached an updated patch that includes this fix. It's my first contribution to Drupal :)

Rerolled against 11.3.x