Here is a paging problem: the data of items in `La...
# compose
c
Here is a paging problem: the data of items in
LazyColumn
comes from two different APIs. “A-API” is the basis of “B-API” so paging requests complete item data is very slow. The data of the “B-API” is not urgently needed. I hope it can be loaded lazily. Is there any way?
Another way to feel bad is to return all the data from “A-API” from the paging, and then request “B-API” data from each item of
LazyColumn
. In order for reuse to take effect (?), I may also need to cache it. It’s dirty...
m
Thought about if there is a way to merge two API’s in repository/viewModel so that you have single source of truth as a data source in your Screen/Composable?
c
Thought about if there is a way to merge two API’s in repository/viewModel so that you have single source of truth as a data source in your Screen/Composable?
No, this is actually Github’s notification API. To get the repository data corresponding to each notification, I must request each subject again once after receiving all notifications.