Is there an existing issue that is already proposing this?
[X] I have searched the existing issues
Is your feature request related to a problem? Please describe it
Any time you want to cache key based on request you need to manually use cacheManager.
For example I have jwt token which is passed in the header and it has some value I need to use in cache key. For this I need to manually create cache object
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
Any time you want to cache key based on request you need to manually use cacheManager.
For example I have jwt token which is passed in the header and it has some value I need to use in cache key. For this I need to manually create cache object
Describe the solution you'd like
It would be nice
@Cache
to also accept callbackExample:
Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
Ease of use