Handling asynchronous effects in reactive contexts like the one you're describing can indeed lead...
When I have an Rx that uses an async Effect
If sourceRx changes and I read derivedRx while it's recomputing, I get back the old value with a waiting flag. But get.result() doesn't seem to care about the waiting flag and returns a stale value immediately without blocking.
I assume this is intended behaviour, but are there any semantics to get strictly correct fresh values same way you would from a sync function? Everything I can think of is kind of hacky, like polling get() until it doesn't return .waiting and doing this at every single call site
If sourceRx changes and I read derivedRx while it's recomputing, I get back the old value with a waiting flag. But get.result() doesn't seem to care about the waiting flag and returns a stale value immediately without blocking.
I assume this is intended behaviour, but are there any semantics to get strictly correct fresh values same way you would from a sync function? Everything I can think of is kind of hacky, like polling get() until it doesn't return .waiting and doing this at every single call site
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
