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?
Chachako
09/11/2022, 6:20 AM
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
Michal Guspiel
09/11/2022, 10:57 AM
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
Chachako
09/11/2022, 2:22 PM
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.