{"version":"2.1.273","anchor":"session-storage-read-cache-now-also-evicts-an-identities","canonical_anchor":"session-storage-read-cache-now-also-evicts-an-identities","heading":"Session storage: read-cache now also evicts an 'identities' map on invalidation","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/session-storage-read-cache-now-also-evicts-an-identities","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Session storage: read-cache now also evicts an 'identities' map on invalidation\n\nSession storage's read cache now also clears a matching identities map when entries are invalidated\n\n**Unclear.** What the identities map is used for and what user-visible effect stale entries would have is not stated.\n\n**What**\n\nAn internal caching component used for session storage now tracks an additional `identities` map. When cached entries are invalidated on the \"read\" path, matching keys are now also removed from this `identities` map, not just from the main cache.\n\n**Why**\n\nThis keeps identity-related cache data from going stale alongside the rest of the invalidated cache, avoiding a case where stale identity data could linger after a read invalidation.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}