Until we can do #1977206: Default serialization of ConfigEntities some day (?), each ConfigEntity type needs to take care of removing their potentially huge runtime properties before serialization.
For EntityDisplays, that includes the instantiated widget/formatter plugins, or the field definitions.
EntityFormDisplay implements _sleep() to take care of that, but the same logic also applies to EntityViewDisplay.
EFDs just more badly need it, since they typically get serialized as part of entity forms, and EVDs don't have that case. Still, EFDs and EVDs should stay symmetrical.
--> the _sleep() implementation should move to EntityDisplayBase
Beta phase evaluation
Issue category | Bug: EntityViewDisplays can be huge if serialized |
---|---|
Issue priority | Normal: AFAIK we don't have a case in core where they do get serialized |
Disruption | None |
Comment | File | Size | Author |
---|---|---|---|
#1 | 2405127-EntityDisplayBase_sleep-1.patch | 1.9 KB | yched |
Comments
Comment #1
yched CreditAttribution: yched commentedPatch
Comment #2
yched CreditAttribution: yched commentedComment #3
yched CreditAttribution: yched commentedComment #4
jibranThanks for the patch and issue.
Comment #5
yched CreditAttribution: yched commentedI changed my my mind and qualified it as a bug in the "Beta phase evaluation" table, but forgot to update the issue metadata accordingly
Comment #6
alexpottCommitted 556d680 and pushed to 8.0.x. Thanks!