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
When any property of LazyList changes on iOS, we invoke collectionView.reloadData(). This is an expensive operation which shouldn't be necessary to call, as we are given atomic change updates within UICollectionViewListUpdateCallback.
Currently, I don't have a lot of confidence in UICollectionViewListUpdateCallback being given the correct atomic change updates. This is due to the lack of tests, and the fact that on Android we invoke notifyDatasetChanged (the equivalent to iOS' reloadData) on a specific code path, further reducing trust that these atomic change updates are correct.
When any property of
LazyList
changes on iOS, we invokecollectionView.reloadData()
. This is an expensive operation which shouldn't be necessary to call, as we are given atomic change updates withinUICollectionViewListUpdateCallback
.Currently, I don't have a lot of confidence in
UICollectionViewListUpdateCallback
being given the correct atomic change updates. This is due to the lack of tests, and the fact that on Android we invokenotifyDatasetChanged
(the equivalent to iOS'reloadData
) on a specific code path, further reducing trust that these atomic change updates are correct.Therefore, I would argue that this is blocked by:
WindowedLazyList
#1497The text was updated successfully, but these errors were encountered: