(graphcache) - Fix offlineExchange timing after rehydration #1019
Conversation
🦋 Changeset detectedLatest commit: 4fcc210 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
| @@ -249,10 +250,15 @@ export const cacheExchange = (opts?: CacheExchangeOpts): Exchange => ({ | |||
| // If no hydration takes place we replace this stream with an empty one | |||
| const bufferedOps$ = hydration | |||
| ? pipe( | |||
| sharedOps$, | |||
| buffer(fromPromise(hydration)), | |||
| combine( | |||
There was a problem hiding this comment.
This works because combine can retroactively still resolve an operation synchronously once the first operation comes in. This lets bufferedOps$ hang in its active state for as long or short as needed.
buffer on the other hand may not emit when its list of values is empty, but would wait for the next signal if then a new event comes in. Because we'd before only wait for one buffer output though and have one input event, there are conditions where bufferedOps$ would stay active indefinitely.
No description provided.