#data integrity

I am seeing this issue. I am using Drupal 11.1.5.

Steps to reproduce:

1. Add a new or use existing content type.
2. On the “Manage fields” tab for the content type, add a new term reference field using the select widget. Save and select the “tags” vocabulary on the field settings form.
3. Create a new node for the content type - also add some term in the "Tags" field.
4. Go back to the "“Manage fields” tab for the content type and delete the term reference field created in step 2.
5. Navigate to the page http://<server>/taxonomy/term/<tid>. You can see the node created in step 3 is still listed for the tag term.

@callumharrod walked us (@lauriii, myself and David Bee) through the designs he crafted. All of us asked various questions. The PoC here is still aligned with the designs, with one exception: we're not going to be exposing a component instance as an exposed slot, but a slot in a component instance.

Walked @phenaproxima through that change, and captured this change with him together, as a way to hand this off to him: https://git.drupalcode.org/project/experience_builder/-/merge_requests/7... :)

(I'm still around, obviously!)

We should be able to remove pattern from the list because patterns are not leaving any references to the config entity; they are always stored as a copy.

Same problem exists for SDCs; there's nothing preventing them from being deleted from the code base 📌 Gracefulness when developing SDCs: SDCs may appear/disappear from one request to the next Active .