IssueTracker

Could you clarify what you mean by for processing?

If you want to react as items are loaded you could try using PagingData.map. If you want to fetch a specific item you could use adapter.getItem(position), but not e that this will trigger fetches and drops based on prefetchDistance. We're looking into some better ways to expose the loaded data as the library is still alpha, so if you could let us know your use-case it would definitely help!

In our case we have "search" feature that works with a recycler view. When user clicks a search result item, we want to check if the item is already loaded (say, in PagingData) so we don't have to invalidate the whole paged data if already loaded. Also we want to make sure the searched item is visible on the screen, so we need to find the position of the item in the loaded list (e.g. PagingData), so that we can scroll the recycler view (scrollToPosition) to the item so it's visible. I think we can achieve these with what you mentioned (PagingData.map or adapter.getItem(position)) but I'm not sure if it's the best option or if it'd work well.

It should work as a stop-gap except for pages getting dropped due to maxSize (default value of PagingConfig.maxSize is unbounded).

I agree that Paging could provide some better ways to allow access to the loaded / presented data though, but we're still investigating the best way to expose that.

We've since been trying with the stop-gaps and it turned out they're not as useful as it seemed. PagingData.map doesn't do much help since we can't reliably associate the items from Paging.map with their corresponding positions in the adapter. Also Adapter.getItem initiating loadAround has turned out to be really problematic for our use case. I think calling loadAround from getItem is maybe too much of a side effect from a getter method. I wonder if you guys considered calling loadAround(i) when the view at the position i is bound?

We've added .snapshot() and .peek() APIs to PagingDataAdapter and AsyncPagingDataDiffer to allow accessing data without triggering page fetch.

This will allow access to the presented data, after transformations. For processing dependent on loaded pages, you should still use PagingData.map { } to ensure transformations don't remove items you need to process.