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.Followup to #2090115: Don't install a module when its default configuration has unmet dependencies
Collections can declared that they support configuration entities however config entity storage is completely unaware of collections. Collections are only used to store config override information by core. I think we should simplify code by removing the ability to support loading and creating config entities in collections.
Beta phase evaluation
| Issue category | Bug because config entity storage is unaware of collections - thereby breaking static caching |
|---|---|
| Issue priority | Normal because the functionality is currently unused and untested - which is another good reason to remove. |
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 2451359.3.patch | 10.88 KB | alexpott |
| #1 | 2451359.1.patch | 9.49 KB | alexpott |
Comments
Comment #1
alexpottRemoved the fake ability of collection's other than the default to support config entities.
Comment #2
alexpottComment #3
alexpottRerolled.
I think removing this is good also because reducing functionality will reduce possible bugs.
Comment #4
BerdirYes, this makes sense.
We've discussed this a while back already, while working on #2090115: Don't install a module when its default configuration has unmet dependencies.
This removes a method from a public interface, but I doubt it's one that anyone ever called or implemented, since it doesn't really work.
Comment #5
catchYes agreed. And not really an API change if the API has never, ever worked.
Committed/pushed to 8.0.x, thanks!