Fixes #48
There was an unneeded shareReplay operator added to the observable returned by the @Cacheable decorated method which caused other calls to the method to reuse the return value of the previous call, even if it was already unsubscribed for.
This was clearly visible when you had multiple routes using async pipes subscribed to cached service methods. Basically, navigating fast through routes, would cause the async pipe to not unsubscribe from the Observable on ngDestroy which caused performance issues. Also, sometimes you could witness stale data due to the same issue.
Thanks @DrakeAnglin for reporting!
Fixes #48 There was an unneeded
shareReplayoperator added to the observable returned by the@Cacheabledecorated method which caused other calls to the method to reuse the return value of the previous call, even if it was already unsubscribed for. This was clearly visible when you had multiple routes usingasyncpipes subscribed to cached service methods. Basically, navigating fast through routes, would cause the async pipe to notunsubscribefrom the Observable onngDestroywhich caused performance issues. Also, sometimes you could witness stale data due to the same issue. Thanks @DrakeAnglin for reporting!