[2.0.6] What do we do with empty definitions?

Created on 22 June 2025, 5 days ago

Problem/Motivation

https://www.drupal.org/project/drupal_cms_olivero has a few challenging quirks including empty component definitions:

# This component is used for search and is not intended to be used within
# Experience Builder, so no metadata is included.

https://git.drupalcode.org/project/drupal_cms_olivero/-/blob/1.2.x/compo...

# This component is used for search and is not intended to be used within
# Experience Builder, so no metadata is included.

libraryOverrides:
  dependencies:
    - core/drupal.autocomplete

https://git.drupalcode.org/project/drupal_cms_olivero/-/blob/1.2.x/compo...

Proposed resolution

What do we do with those? We ignore them in the ComponentSelector? Let's not ignore them at the ComponentPluginManager's discovery level, in order to not break projects using those components in Render API or Twig includes.

📌 Task
Status

Active

Version

2.0

Component

Code

Created by

🇫🇷France pdureau Paris

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024