You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems as if the RemoteMediator class can't be implemented with cash app paging? If this is true, that would be really sad, as it's the most valuable part of the AndroidX paging library that it's trying to mimic.
The issues arise when trying to implement the actual classes:
1.
Type mismatch.
Required:
RemoteMediatorMediatorResult
Found:
RemoteMediatorMediatorResultSuccess
RemoteMediatorMediatorResult is the expected return type, but can't be initialised. The natural inclination is to use the RemoteMediatorMediatorResultSuccess (which can be initialised) or RemoteMediatorMediatorResultError (which can be initialised), but the method:
@JakeWharton
Hi Jake,
I understand no one is working on this repo. Does that mean issues aren't getting solved / answered anymore? Is it temporary that no one is working on it anymore? And is there a newer paging library that's being worked on? Would love if someone could guide me on this issue #273.
Kind regards
It seems as if the
RemoteMediator
class can't be implemented with cash app paging? If this is true, that would be really sad, as it's the most valuable part of the AndroidX paging library that it's trying to mimic.The issues arise when trying to implement the actual classes:
1.
RemoteMediatorMediatorResult
is the expected return type, but can't be initialised. The natural inclination is to use theRemoteMediatorMediatorResultSuccess
(which can be initialised) orRemoteMediatorMediatorResultError
(which can be initialised), but the method:doesn't accept it.
The same issue arises when implementing the
Pager
. Methods expects:PagingSourceLoadResult
:Naturally, using the class
PagingSourceLoadResultPage
(instead of the originalLoadResult.Page
from AndroidX Paging, doesn't work for the same reason.Here's the full codebase of all the classes:
The text was updated successfully, but these errors were encountered: