I've used cacheables in a prior project and like how it works, but was surprised to analyze the source code and discover that there is no active eviction.
Upon maxAge being reached, a cacheable item will be refreshed. But if the item (ex: a JWT authorization that has been refreshed) is no longer queried, the cacheable remains in memory forever.
I have implemented an optional eviction feature for policies with maxAge on a copy of cacheables in my project. Can I contribute this back?
I've used cacheables in a prior project and like how it works, but was surprised to analyze the source code and discover that there is no active eviction.
Upon maxAge being reached, a cacheable item will be refreshed. But if the item (ex: a JWT authorization that has been refreshed) is no longer queried, the cacheable remains in memory forever.
I have implemented an optional eviction feature for policies with
maxAgeon a copy of cacheables in my project. Can I contribute this back?