You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the previous versions of ngx-hateoas-client, the cache is activated (true) by default. For individual calls, the cache can be (de)activated by GetOptions (useCache).
If required, the cache can also be disabled globally by HateoasConfiguration.cache.enabled. In this case, the caching is deactivated - even if GetOptions.useCache = true is set.
If you now want to develop an application that executes all calls without caching by default and only one specific call with caching, then useCache: false must be set in all calls.
Feature request:
Introduced a possibility to set the default value for GetOptions.useCache. Completely independently, however, there should still be the option of hard deactivating the cache for all methods via the HateoasConfiguration.
The text was updated successfully, but these errors were encountered:
In the previous versions of ngx-hateoas-client, the cache is activated (true) by default. For individual calls, the cache can be (de)activated by GetOptions (useCache).
If required, the cache can also be disabled globally by HateoasConfiguration.cache.enabled. In this case, the caching is deactivated - even if GetOptions.useCache = true is set.
If you now want to develop an application that executes all calls without caching by default and only one specific call with caching, then useCache: false must be set in all calls.
Feature request:
Introduced a possibility to set the default value for GetOptions.useCache. Completely independently, however, there should still be the option of hard deactivating the cache for all methods via the HateoasConfiguration.
The text was updated successfully, but these errors were encountered: