IssueTracker

Artifact used: androidx.paging:paging-runtime & rxjava2 Version used: 3.0.0-alpha02

In order to call pagingSource.invalidate() to deal with the user of my app deleting a row from the paged RV they're looking at, I had to do the following in my ViewModel:

    private var pagingSource: PagingSource<Int, FeedItem>? = null
    private val feedPagerObservable by lazy {
        Pager(
                config = PagingConfig(pageSize = 20),
                pagingSourceFactory = { pagingSourceFactory.create(...).also { pagingSource = it } }
        ).observable
    }

Then, elsewhere in the VM I have a reference to the source to call invalidate. This feels really, really ugly. I'm aware that I have to pass a factory into Pager because it can get recreated, but this feels like it's not something I should really have to worry about.

It's hard to say what I would prefer, which is why I imagine it's like this!

Keeping a reference to the Pager feels less gross than it does for PagingSource. Perhaps Pager could internally keep a reference to the existing PagingSource so I could just call Pager.invalidate() and it would do a similar hack internally?

Very happy for better or other suggestions. Currently it feels very awkward, and it was super hard to discover that the .invalidate() method even existed to call!