- 🇨🇭Switzerland berdir Switzerland
Closing this as won't fix/duplicate of 📌 Deprecate CacheBackendInterface::invalidateAll() Active , which deprecated invalidateAll(), the other two can be useful and aren't really a problem to implement.
There is an invalidate* functions on the cacheBackendInternface however I don't see a) it used, b) a usefulness to include this over their equivalent delete function. Is there ever a need to pull an expired cache?
May as well save the memory/database storage by deleting it over setting its expiration time and remove this api (or map it to delete*).
Closed: duplicate
11.0 🔥
cache system
Refactors an existing API or subsystem for consistency, performance, modularization, flexibility, third-party integration, etc. May imply an API change. Frequently used during the Code Slush phase of the release cycle.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Closing this as won't fix/duplicate of 📌 Deprecate CacheBackendInterface::invalidateAll() Active , which deprecated invalidateAll(), the other two can be useful and aren't really a problem to implement.