Following on from discussion started on Cache issue persists after update to 8.x-2.0-alpha2 🐛 Cache issue persists after update to 8.x-2.0-alpha2 Closed: outdated it was decided the below considerations should be moved to a new issue.
ConfigSubscriber::setUncacheableEntityTypes() currently does a check of all entity types which doesn't seem very efficient. Consider refactoring this method to only operate on the entity type containing the field that has had its configuration saved.EntityTypeCacheableManager service (for lack of a better name) to consolidate the entity type cache property related logic.field_encrypt_entity_type_alter() to use the EntityTypeCacheableManager service\Drupal\field_encrypt\EventSubscriber\ConfigSubscriber::setUncacheableEntityTypes() to use the EntityTypeCacheableManager service and only affect the entity type containing the field who's configuration was updated.Closed: outdated
2.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Since 2.x is no longer being developed and the Uncacheable concept was removed from 3.x ( https://www.drupal.org/project/field_encrypt/issues/3153125#comment-1390... 🐛 Cache issue persists after update to 8.x-2.0-alpha2 Closed: outdated ), I'm closing this issue.