Vlad Ioffe

@EskoCruz, can you pls give a full example?

+1

@Nemo9439 any suggestions?

@tripodsgames, I would like to avoid that because of the different configuration options that the different decorators have. Any other suggestions?

I think it would be better to have such configuration on the app level and not inside the lib. As there are multiple ways in which you could provide the...

hi @rdhainaut, for both decorators you can pass your own cache object (see here https://vlio20.github.io/utils-decorators/#memoize) under the cache attribute of the config object. That way you can control the cache...

Do you mean to have a decorator to which you provide the same cache as you are providing to the memorize decorator?

I understand your intent but there has to be a way to connect between the two decorators memoizeAsync and burstMemoizeAsync. What will happen if you have 2 methods in your...

The key resolver is responsible for setting the key in the cache. It is agnostic to the cache it is working with. An alternative (if you don't pass your own...

It is not a global object as you might have multiple caches. I think the best approach is the one that is already implemented with the cache property and the...