Problem/Motivation

Config entity types have no concept of being "installed", that they are even able to be so is kind of an oversight. Getting installed as opposed to just the regular definitions has no benefit but causes extra cache/query lookups, especially with removing the caching from getLastInstalledDefinitions() in #3617152: EntityLastInstalledSchemaRepository::getLastInstalledDefinition() loads all definitions

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

berdir created an issue. See original summary.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Title: Use use regular entity type definitions as opposed to installed definitions » use regular entity type definitions as opposed to installed definitions
berdir’s picture

berdir
Primary language German
Location Switzerland
commented

On D11, the whole service can possibly be dropped completely. You can have two hooks, one first, one last, then all of this should be unecessary? it's in theory possibly to bypass that, but someone would need to explicitly set that up.