You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am currently implementing some custom SharedReaderKey that does not have a concept of "load", but just the capability for subscribing to the data.
For this reason I used continuation.resumeReturningInitialValue for my load endpoint.
This of course means, that when I call load on my shared instance with that key, it always throws the internal load error.
My question would be:
Is there the possibility to still allow the load in that case, but fallback to the subscriber to wait for its first result?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am currently implementing some custom SharedReaderKey that does not have a concept of "load", but just the capability for subscribing to the data.
For this reason I used
continuation.resumeReturningInitialValuefor my load endpoint.This of course means, that when I call load on my shared instance with that key, it always throws the internal load error.
My question would be:
Is there the possibility to still allow the load in that case, but fallback to the subscriber to wait for its first result?
Beta Was this translation helpful? Give feedback.
All reactions