Only allow deleting Code Components if there's 0 usages

wim leers → credited catch → .

Closed 🐛 Trying to remove code component from page immediately after attempting to edit it gives 404 error Active as a duplicate of this.

Scenario that needs to be addressed with this fix :

• Create code component named {code01}
• Create code component named {code02}
• Import code01 to code02
• Delete code01 able to delete code01
• Code02 gives error as below

Could we make the soft delete as an explicit feature? I.e. hiding modules from the UI. I think this would be really useful in the beginning until we can associate which users can use which components. Tagging with needs follow-up for that.

We could still offer the delete as an option because there are scenarios where it's desired to delete a component and all of its uses altogether. However, there's a difference between content vs components referring to components. I'd say that uses of a component in another component should prevent deleting, but deleting a component used in content should not prevent the deletion (especially because even past revisions would prevent deletion).

What would be extremely useful is having a list of usages of the component. This is not only useful for the delete use case but also when you want to assess how components are being adopted.

I tested #7.

To clarify, this is not an issue when the components are stored (e.g. I publish them, even without "adding to components" aka status=1), only on the transient time when they are in auto-save, not published, not status=1, as we do this validation on config entity dependencies. That part IMHO is Works as designed, as the preview message is informative enough to fix the situation.

The original purpose of this issue still remains though.

It seems this is kind of a duplicate of ✨ Usage info for code components with unpublished changes Postponed (because it's hard to find).

@lauriii in #8:

What would be extremely useful is having a list of usages of the component.

We already have that infrastructure and information, since 📌 Calculate field and component dependencies on save and store them in an easy to retrieve format Active . We just don't have it in the modal dialog, which is what I suspect you're hinting at?

If so, that makes this even more closely related to ✨ Usage info for code components with unpublished changes Postponed !

Could we make the soft delete as an explicit feature?

Yes, but what does "explicit feature" mean? 👈 confused me even more, perhaps you meant "components"?