Status Update
Comments
es...@gmail.com <es...@gmail.com> #2
there are some image for help
el...@google.com <el...@google.com> #3
hello?
es...@gmail.com <es...@gmail.com> #4
Here, you can start from MainViewModel.itemsState
until you reach Dao.getItemsPagingSource
. This can be rendered through ItemsScreen
.
I think you can ignore the RemoteMediator
.
However, the behavior here seems different from MainViewModel.modelsState
. One thing that could be noted here is that when switching filters and the list has new items above the current item on top, The list doesn't move up until you switch again to another filter that has similar result. For example, selecting R10
then No Radius
then R100
.
Upon careful observation, I think PagingData<T>.map
and PagingData<T>.insertSeparators
in HeaderItemRelationPagingDataMapper
greatly contributes to the bug in MainViewModel.modelsState
so I might have to report this on
Description
Component used: androidx.room:room-paging Version used: 2.6.1
I have here a repro project which is quite consuming to build. I am using the paging library with remote mediator. Everytime I update my query, the list changes and somehow removes the 1st item then shows the 2nd item instead then you can scroll up to see the 1st item. I think the 1st item gets removed from the list then is readded a bit later which you can see from the animations. I tried this with static results using
PagingData.from
but it doesn't happen and shows the expected behavior except without animations