Cache tags for *all* config entities

Created on 22 September 2014, over 10 years ago
Updated 4 January 2025, 16 days ago

Problem/Motivation

Before Drupal 8 ships, we want to ensure that all entity cache tags work correctly. Every content entity (well, except contact_message, which is never stored or rendered) already has test coverage. They're arguably also the most complex ones.
But, config entities are also very important. Without proper cache tag bubbling and test coverage, it's extremely likely that many bug reports will be filed about things "not working", due to necessary cache tags not being associated.

Worse, yet: without proper cache tag invalidation, it will seem like CMI deployments are broken! When changing config ("things in CMI") through the UI, the invalidation is performed by the UI, not by the config system!

Proposed resolution

Add test coverage for all config entities that don't already have test coverage.

Remaining tasks

User interface changes

None.

API changes

None.

🌱 Plan
Status

Closed: outdated

Version

11.0 🔥

Component

configuration entity system

Created by

🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

Live updates comments and jobs are added and updated live.
  • Performance

    It affects performance. It is often combined with the Needs profiling tag.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇨🇭Switzerland berdir Switzerland

    I don't think we benefit from this issue still being open. It's been untouched since almost 10 years now. We've plenty of direct and indirect test coverage. It's not technically been fixed, so I'm closing it as outdated.

Production build 0.71.5 2024