Assigned
Status Update
Comments
yb...@google.com <yb...@google.com> #2
Hello, can you please attach a sample that reproduces your error?
du...@google.com <du...@google.com> #3
I’ve attached two screen recordings demonstrating the mediator's behavior during the first and second launches after installation. Additionally,
Description
androidx.paging:paging-runtime-ktx:3.0.1
androidx.paging:paging-compose:1.0.0-alpha12
Will be describing issue with Jetpack Compose example:
Currently we're forced to use
val isRefreshing by remember { derivedStateOf { games.loadState.refresh is LoadState.Loading } }
val isErrorOnFirstPage by remember { derivedStateOf { games.loadState.refresh is LoadState.Error } }
val isError by remember { derivedStateOf { games.loadState.append is LoadState.Error } }
Inside the composables. It would be great if we could observe these events in places where we are declaring our Flow<PagingData<Value>>, Pagers. This would allow to propagate these important events from upside down, not the other way around.
The only workaround I can currently see ( if one doesn't want to emit these events from the view layer ) is passing lambdas into the PagingSource. But this should create quite an overhead.
Any enhancement of the Paging API's would be a big plus.