Closed SteffRhes closed 1 year ago
WIth the introduction of new abstract classes I needed to avoid caching redunancies between them so I already started work on this. Will be pushed with my current work on the triple form refactoring.
This module bundles logic which previously resided in AbstractEntity
and GetContentType
, and it should be our single focal point for everything caching-related from now on.
We should utilize ad-hoc caching much more throughout the code-base to improve performance.
Currently there are some scattered modules / classes / functions in use already, like
GetContentTypes
and several functions inAbstractEntity
(which will be redundant or conflicting soon with various other Abstract classes to come). Also in my current form refactoring I implemented an autcomplete caching for properties.I suggest to collect various caching functions in one place, probably under
apis_core/helper_functions
.