Since the release of paging3, any plan to adapt it 馃槈?
TonnyL
All 5 comments
If they choose to adapt paging3 it should be independent from paging2 for the folks that won't migrate to it, on the other hand i don't really see an easy way for the adoption, since paging3 does most of the logic on the required PagingDataAdapter, wouldn't it make necessary for epoxy to extend it? Unfortunately PagingData has a lacking API :(
EDIT: after looking more into the doc noticed that there is an AsyncPagingDataDiffer, so it's easier than I thought.
0rp3u
on 15 Jul 2020
@elihart any ETA or plan on this?
anhanh11001
on 11 Aug 2020
I don't have any plans to do this myself, as we don't use Paging and it was mainly contributed externally. I'd be open to reviewing a pull request if somebody wants to contribute it (in a clean, backwards compatible way)
elihart
on 11 Aug 2020
There is the pull request for this feature - #1096
osipxd
on 8 Dec 2020
There is a pull request for this feature - #1096
@elihart Any plans on when a review of the PR will happen?, we are a company with 150.000 customers very keen on using the Paging3 alpha in our app as fast as possible.
andybdahl
on 13 Jan 2021
Related issues
jQrgen
路
5Comments
fredo-
路
4Comments
Sergiyss
路
6Comments
AdamMc331
路
6Comments
atonamy
路
4Comments
Most helpful comment
If they choose to adapt paging3 it should be independent from paging2 for the folks that won't migrate to it, on the other hand i don't really see an easy way for the adoption, since paging3 does most of the logic on the required PagingDataAdapter, wouldn't it make necessary for epoxy to extend it? Unfortunately PagingData has a lacking API :(
EDIT: after looking more into the doc noticed that there is an AsyncPagingDataDiffer, so it's easier than I thought.