Replies: 1 comment 9 replies
-
|
Any reason you are not using the new request result feature? |
Beta Was this translation helpful? Give feedback.
9 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Using request caching, the custom operator returned by
createRequestsCacheOperator()expects a string as argument for the cache key. Suppose the key needs to be a compound key with a value from upstream the observable. This could be some parent ID that identifies a sort of nested store cache for that parent. For instance:Would it be possible with an overload, or separate operation function, that passes along emitted values (but still expects a cache key to be returned)? Something along the lines of:
Beta Was this translation helpful? Give feedback.
All reactions