User data service does not take cache tag invalidation into account

Created on 25 April 2015, about 9 years ago
Updated 27 December 2023, 6 months ago

Problem/Motivation

The User data service offers a public API to store additional data related to individual users. The related UserDataInterface exposes two methods that perform storage writes: set() and delete(). The default implementation does not take cache tag invalidation into account, which may cause stale cache entries not to be invalidated.

Proposed resolution

Add cache invalidation to UserData::set() and UserData::delete().

๐Ÿ› Bug report
Status

Needs work

Version

11.0 ๐Ÿ”ฅ

Component
User systemย  โ†’

Last updated about 12 hours ago

Created by

๐Ÿ‡ฎ๐Ÿ‡นItaly plach Venezia

Live updates comments and jobs are added and updated live.
  • Needs tests

    The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.

Sign in to follow issues

Merge Requests

Comments & Activities

Not all content is available!

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

Production build 0.69.0 2024