PHP Error after deleting all built-in components

Field field_xb_demo is unknown.

👆

This is a clear tell that you've deleted a FieldConfig entity 😜

You probably deleted one of the three config dependencies for that field instance:

…
dependencies:
  config:
    - experience_builder.component.experience_builder+image
    - experience_builder.component.experience_builder+my-hero
    - experience_builder.component.experience_builder+two_column
…

Deleting the hero one for example triggers:

Conceptually related issues linked.

Woah 🤯 I didn't notice this when I was deleting the components. This seems like a fairly severe problem because I assume it deleted all of the XB content as a result?

Didn't intend to remove the related issue.

#4: that's how config dependencies work.

You must first update that config, then delete it. You were informed of the consequences. That's not severe, that's intentional.

We could implement \Drupal\Core\Config\Entity\ConfigEntityBase::onDependencyRemoval() to remove that component from the tree. But that too won't always work: if the component being removed contains components in its slots, then we wouldn't know how to remove it sanely. ⇒ It's better to ask the Site Builder to update the config first.

Even more so once the slot restrictions mentioned in 📌 [SPIKE] Comprehensive plan for integrating with SDC Active are a reality: then it becomes very likely that contained components cannot simply be moved "up a level".

Only simple scenarios could be covered by \Drupal\Core\Config\Entity\ConfigEntityInterface::onDependencyRemoval() — i.e. for deleting leafs of the (default) component tree.

Repurposing this issue to handle those simple scenarios.

🐛 Cannot delete JS components due to component depending on them Active implemented this! And it was able to do so thanks to 📌 [later phase] Support props defaults that have config dependencies Postponed .