Right now, a bundle config entity type could serve as bundle only for one content entity type. E.g. node_type is used for node but cannot be used by a custom content entity type in the same time with node. Some contrib/custom modules show that it's a real use-case to have a bundle config entity type shared across many content entity types. See the Entity Pilot case.
Recently, I hit a case when I need a new content entity type that extends taxonomy_term. But I still want to use vocabulary as bundle for the new entity type while it remains available for core, taxonomy_term, term entity type. The two content entities should coexist and share the same bundle config entities.
The limitation is by design, as the bundle entity type bundle_of annotation is a string rather than an array of strings.
EntityTypeInterface::getBundleOf() with a new EntityTypeInterface::getBundleOfEntityTypeIds() method that returns an array of content entity type IDs.EntityTypeInterface::getBundleOf().bundle_of annotation as sting.To be decided: How to resolve the field_ui_entity_operation() case, where there the content entity type context lacks, so there's now way to figure out which is content the entity type to pick up.
Figure out how to handle the field_ui_entity_operation() case.
None.
EntityTypeInterface::getBundleOf() method.EntityTypeInterface::getBundleOf() is deprecated.bundle_of annotation as sting is deprectaed.None.
TBD.
Closed: won't fix
10.1 ✨
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.