Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Consider integration with Paging library once it is stable

See original GitHub issue

See https://medium.com/@Zhuinden/live-paged-lists-architecture-components-and-room-or-realm-268c9299a661

and

https://github.com/Zhuinden/realm-helpers/blob/4b83911b20304355e95870e51a1743bc141a36fd/realm-pagination-example/src/main/java/com/zhuinden/realmpaginationexample/data/dao/TaskDao.java#L25-L28

Although I’m sure the API can be nicer (not having to explicitly open/close, and while keep the notification could be moved to a background handler thread, but otherwise use refresh() in the do { while loop on the io() scheduler of the computable live data.

Issue Analytics

State:
Created 6 years ago
Comments:22 (12 by maintainers)

Top GitHub Comments

4reactions

BapNesScommented, Mar 12, 2019

Hi everyone,

To be consistent and use support libraries, I’m wanting to implement Paging support library because I need to fetch data from the API when needed. LivePagedListBuilder require DataSource and PagedList.BoundaryCallback implementations.

Because previous comments are 5 months old, I just wanted to know if an official RealmDataSource is on a way or not at all ?

I think it would be nice to have one, like ObjectBox do for example.

Thanks.

Paging-01

3reactions

cmelchiorcommented, May 22, 2018

@mhdtouban Sorry, I was mainly thinking about the use case where you had all data stored locally. I do agree that the paging library nicely provides a lot of utility where you need to fetch the data from the server first.