Prevent the deletion of a bundle entity if there are existing content entities of that bundle

Adding hidden patch file of merge request which is a reroll against 11.x

https://www.drupal.org/files/issues/2024-01-30/2413769-47.patch →

If the module's configuration is set up correctly, when uninstalling a module, all associated configurations, such as custom content types defined in files like node.type.my_bundle_name.yml, are being uninstalled automatically. This happens regardless of whether there is existing content using these configurations. As a result, content types are removed without any checks for existing nodes of these types, leading to potential data integrity issues.

Because we use the recommended way of adding dependencies to config files to allow uninstalling config when its parent module is uninstalled.

dependencies:
  module:
    - my_module
    - node
  enforced:
    module:
      - my_module

This is a blocker for ✨ [PP-3] JSON:API DELETE support for config entities Active . Ideally, this would be just another validation constraint in config schema. What's tricky is that validation constraints today are not aware of the operation … and more importantly: when deleting an entity, no validation is happening at all. Interesting challenge!

So perhaps this should indeed not happen in a constraint, but in the actual entity operations? 🤔 Tricky.

( ✨ [PP-3] JSON:API DELETE support for config entities Active was split off from ✨ [PP-2] POST/PATCH config entities via REST for config entity types that support validation Needs work .)