Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
In comment #55 in #2630732: Implement Entity::fields() for migration destinations joachim mentioned that default_bundle was something created for that patch. It isn't, it is a Destination plugin configuration but not documented in Entity.
Steps to reproduce
Proposed resolution
Add the documentation.
Remaining tasks
Patch. review, commit
Comment | File | Size | Author |
---|---|---|---|
#2 | 3171510-2.patch | 1.52 KB | quietone |
Comments
Comment #2
quietone CreditAttribution: quietone as a volunteer commentedA simple patch
Comment #3
mikelutzIt is odd to me that this is defined in Entity. I've looked at the relationships between Entity and EntityConfigBase and EntityContentBase before and thought they were wonky, and this just makes me want to mention it again. I realize there are reasons with the derived entity destinations, but with EntityConfigBase and EntityContentBase both inheriting from Entity, it is so strange to me to be dealing with bundles in Entity, and then overriding that behavior in EntityConfigBase to not use them, rather than to put the bundle stuff into EntityContentBase to begin with.
Anyway, that rant has nothing to do with this issue, the documentation here is good to go.
Comment #4
alexpottCommitted and pushed bf5aa399de to 9.1.x and 38f194be1d to 9.0.x and 73345f7556 to 8.9.x. Thanks!
Backported to 8.9.x since this is a docs fix.