Closed SPiercer closed 2 months ago
Why would you not just await a .refresh/reload?
.refresh/reload does wait for the internal execution to complete. It just updates the state on each update
.refresh/reload does wait for the internal execution to complete. It just updates the state on each update
It doesn't I tried it.
even the code it doesn't await any asynchronous calls.
That should be unintended behavior then. I will write a test to validate expectations first
any updates ?
Preparing for IO connect but should be able to address in the next few weeks
Hello @rodydavis I've came around again after your recent releases and this issue still persists.
awaiting .refresh
or .reload
does not waits for the future/computation to finish, i have to rely on my implementation to actually await for the future to recompute again
can we reopen this PR or do something about it?
Added
.refreshAndAwait()
toFutureSignal
in order to do.refresh()
but instead of it just changing the state it awaits the future to recompute and finishes the refreshinggood for drag down to refresh indicators and other loading indicators that rely on completing futures since isRefreshing/isReloading is different than isLoading