Open anhanh11001 opened 4 years ago
Honestly, with the new Frozen results support, I'd rather just love to remove the paging support from Monarchy entirely. :thinking:
But AFAIK the exposure as PositionalDataSource
is needed for Paging 3.0 specifically in order to make a RealmResults be exposed as a PagingSource in order to be able to combine it with a RemoteMediator, so it's not entirely off the table.
The tricky thing is that Paging 3.0 drags in Kotlin, so I'd probably have to make it an optional module this time, unlike how I'm doing it now. I don't really want to provide a dependency against an alpha library version though (Paging 3 is currently alpha7).
Any plan or idea on supporting Paging 3.0?