-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Firebase Database Paging Support - [New Feature-Pagination] #1601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
@PatilShreyas thanks for filing this! So since you based this on the Firestore adapter, does that mean the tradeoffs are the same? In particular, does the adapter ignore realtime updates? |
Yes. Till now, it does not support realtime updates. |
@PatilShreyas ok in that case I'd be happy to review this feature! Can you send a Pull Request with the target branch as |
@samtstern Thank you ! |
Implementation of Paging for Firebase Database
@samtstern I have updated code as you suggested here #1603 |
Fixed some code and minor changes.
…se#1601 Added functionalities : 1. retry() : Retry the loading of data in RecyclerView after failure. 2. refresh() : Reload data in RecyclerView by clearing recent loaded data.
This has been fixed and released in |
Does the adapter support realtime updates now? |
Firebase Realtime Database has FirebaseRecyclerAdapter to show Data Items in RecyclerView. But, the issue is it has not Paging support added until now. I have developed a solution on Pagination of Firebase Database in RecyclerView on below repository with library code and sample app.
https://github.com/PatilShreyas/FirebaseRecyclerPagination
I referred source code of FirestorePagingAdapter while developing the solution.
FirebaseRecyclerPagingAdapter is built on top of Android Paging Support Library.
So, I request you to please permit me to add this feature in the official FirebaseUI library to help developers with this paging library to load data in pages.
Can I fork this repository and make this feature available?
The text was updated successfully, but these errors were encountered: