As described in #92, the internal caching is flawed, even when using listStrategy: 'always'.
Additionally to the issue with find, this also affects get calls:
The hash value used to cache responses is based solely on the id and ignores params. This leads to problems, when using client side params to e.g. populate different fields on get calls.
Expected behavior
get calls with different params should result in actual new calls to the backend
Actual behavior
get calls with different params return a cached response when an existing call for the same id exists
System configuration
Backend uses params on get requests to populate different fields
Module versions (especially the part that's not working):
feathers-reactive 0.7.2
Steps to reproduce
As described in #92, the internal caching is flawed, even when using
listStrategy: 'always'. Additionally to the issue withfind, this also affectsgetcalls:The hash value used to cache responses is based solely on the id and ignores params. This leads to problems, when using client side params to e.g. populate different fields on
getcalls.Expected behavior
getcalls with different params should result in actual new calls to the backendActual behavior
getcalls with different params return a cached response when an existing call for the same id existsSystem configuration
Backend uses params on
getrequests to populate different fieldsModule versions (especially the part that's not working): feathers-reactive 0.7.2
NodeJS version: 10.10.0
Operating System: macOS 10.13.5
Browser Version: Google Chrome 71.0.3578.98
React Native Version: x (using Angular 7.0.0)
Module Loader: