Disable Caching for test envs about utils-decorators HOT 6 OPEN

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 configuration to the different decorators.

As more as I am thinking about a global configuration the less I want it to be part of the lib.

from utils-decorators.

@Nemo9439 any suggestions?

from utils-decorators.

@Nemo9439 any suggestions?

@vlio20
I'm testing a branch with a global configuration object, so we can modify the settings at a global level.
EX:

Config.Global.disableCache = true;

I want your opinion on this

from utils-decorators.

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

from utils-decorators.

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

And a base configuration per decorator?
EX:

memoizeAsync.DefaultSettings.disableCache = true;

It would even be useful to configure a default configuration.
EX:

memoizeAsync.DefaultSettings.expirationTimeMs = 10000;

from utils-decorators.

This issue is already old, maybe it should be closed. But anyway, my suggestion to @Nemo9439 is to write a wrapper decorator which does what he needs. I did something similar in this stackblitz

from utils-decorators.