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
Prior to version 2.5.0, we used isUpdating to determine the loading state of an ArrayProxy resulting from findAll. The reason for using isUpdating is that other states, such as isFulfilled, were not triggered during background loads.
To be clear, since version 2.5.0, isUpdating returns false when it used to return true. It used to return true when: (1) the findAll promise was resolving, where reload: true was set, and (2) the records were being (re)loaded in the background for ordinary findAll operations.
Did we miss an API change, or perhaps is there a better way of tracking the loading state of an ArrayProxy resulting from a find operation?
The text was updated successfully, but these errors were encountered:
@kbbpartners this regression should be fixed once #4386 is merged and a new version 2.5.3 is released. Many thanks for reporting this and sorry for the inconvenience.
Prior to version 2.5.0, we used
isUpdating
to determine the loading state of an ArrayProxy resulting fromfindAll
. The reason for usingisUpdating
is that other states, such asisFulfilled
, were not triggered during background loads.To be clear, since version 2.5.0,
isUpdating
returns false when it used to return true. It used to return true when: (1) thefindAll
promise was resolving, wherereload: true
was set, and (2) the records were being (re)loaded in the background for ordinaryfindAll
operations.Did we miss an API change, or perhaps is there a better way of tracking the loading state of an ArrayProxy resulting from a find operation?
The text was updated successfully, but these errors were encountered: