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've run into a situation where I want to know when the paginate-remote-array starts loading in fetchContent and when it ends. I'm not sure with the current execution that there's a way to then() the promise that is created internally.
There seems to be two places where PaginatedRemoteArrays are created. The initial load is created in the remote mixin in findPaged. This first call is certainly thenable, but successive calls are then created inside the paginated-remote-array class do not have a mechanism for observing or then'ing.
My questions:
how can we redesign this system so it uses a single source for the promise, making all promises consistently then'able.
should we add additional triggers to the remote-array instead?
The text was updated successfully, but these errors were encountered:
I've run into a situation where I want to know when the paginate-remote-array starts loading in
fetchContent
and when it ends. I'm not sure with the current execution that there's a way tothen()
the promise that is created internally.There seems to be two places where
PaginatedRemoteArray
s are created. The initial load is created in the remote mixin infindPaged
. This first call is certainlythen
able, but successive calls are then created inside the paginated-remote-array class do not have a mechanism for observing or then'ing.My questions:
then
'able.The text was updated successfully, but these errors were encountered: