problem with extended methods about ts-cacheable

[angelnikolov]

Yes, it is.
https://github.com/angelnikolov/ngx-cacheable/blob/dc1c2cc90cbd09f9209a82632a161ce49fa12466/common/index.ts#L8

[jmls]

oh unless I supply my own DEFAULT_CACHE_RESOLVER ;) maybe that will work

[jmls]

no, it doesn't as decorators only work on the class definition, not instance.

however there is a dirty little hack .. if you add this line

parameters.push(this);

just under these lines (lines 79 of cacheable.decorator.ts)

  (propertyDescriptor.value as any) = function(..._parameters) {
    let parameters = JSON.parse(JSON.stringify(_parameters));
    parameters.push(this);

then you get the instance of the sub-class from which you can then grab whatever you need to make the cache comparison

I don't know if this breaks stuff - but it is a simple, non-obtrusive way of getting the sub class instance into the cache resolver

[cyberbobjr]

Hi,
Sorry for the necropost, but does this trick was implemented in the current version of Ngx-cacheable, because it might be usefull for my project :)

[cyberbobjr]

you're great ! many thanks for your job 😄