Open TonnyL opened 4 years ago
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.
@elihart any ETA or plan on this?
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)
There is the pull request for this feature - #1096
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.
Since the release of paging3, any plan to adapt it 😉?