New component requirement: obsolete SDCs must not be auto-added, but must be auto-updated

• +1 for not auto-adding
• -1 for not auto-updating
• And needs a follow-up for auto-deleting if and only if there is zero usage — but for that we'll first need component usage tracking — which requires the "component present in tree" equivalent of 📌 Prevent fields from being deleted if they are used in Experience Builder field's dynamic prop values Active (which does "field type present in props".

Oh and … I guess the "hide them" piece is still important too: we'd have to update \Drupal\experience_builder\Controller\SdcController::getComponentsList() to do that, but that'd require being able to know for a given Component config entity whether it should be displayed or not.

This seems perfect for \Drupal\Core\Config\Entity\ConfigEntityInterface::enable() + \Drupal\Core\Config\Entity\ConfigEntityInterface::disable()? i.e. when a component becomes obsolete, we'd disable() it?

I defer to @f.mazeikis :)

📌 New component requirement: each SDC prop must have StorablePropShape Active is in — making this much more actionable!

+1 to using enable()/disable() for now
Implementing a new requirement "must not be obsolete" for auto-adding is simple enough
Auto-delete needs in-use tracking, as per #3 📌 New component requirement: obsolete SDCs must not be auto-added, but must be auto-updated Active .

Based on #3454125-75: Implement temporary design system for the DrupalCon Barcelona demo → , bumping this to . The ability to ::disable() a Component config entity would be a huge productivity boost for the fine folks working on https://www.drupal.org/project/demo_design_system → 🚀

Still needs the follow-up mentioned in #3.

Just confirming that this is working as expected. Thanks!

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