CryptoTweets | 📰🥇 | Android library

Is background threading managed automatically with PagingData as it is with PagedList, and then returned on the main thread?

From the logs below, it appears PagingData is not run on the backgroud thread in the Paging 3 library compared to PagedList in Paging 2's library.

Expect (Based on the Paging Codelab sample)

• GithubPagingSource override suspend fun load(...) to run on an IO thread.
• SearchRepositoriesActivity viewModel.searchRepo(query).collectLatest { ... } to run on the main thread.

Observe

• Both GithubPagingSource override suspend fun load(...) and SearchRepositoriesActivity viewModel.searchRepo(query).collectLatest { ... } run on the main thread.

Threading is handled on the background by PagedList with toLiveData according to the documentation.

If you use LivePagedListBuilder to get a LiveData, it will initialize PagedLists on a background thread for you.

The Paging 3 documentation does not mention how threading is managed. However, from the logs, PagingSource appears to be running the network request on a main thread and returning the PagingData on a main thread.

I've recreated the Codelab pattern in the CryptoTweets sample app app-simple module.

FeedPagingSource.kt