If a xb config entity (pattern/code component/asset library) is used in a experience builder field there is nothing stopping the configuration from being deleted.
TBD.
📌 Prevent modules from being uninstalled if they provide field types used in an Experience Builder field Fixed can provide hints for defining a resolution.
We need also to take into account what should happen when we are syncing config from another environment.
Should we fail the config import? Should we just fail gracefully on rendering that component (as in current "broken/missing block")?
Active
0.0
Component sources
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 .