Hi, your package is very useful and awesome. I'm wondering if you could add ability to add a widget in between the listviews after certain number of items. Thanks.

return PaginateFirestore( //item builder type is compulsory. itemBuilder: (context, documentSnapshots, index) { final data = documentSnapshots[index].data() as Map; print("index $index"); return Expanded( child: ListTile( leading: CircleAvatar(child: Icon(Icons.person)), title: data == null ? Text('Error in data') : Text(""), subtitle: Text(""), ), ); }, // orderBy is compulsory to enable pagination query: FirebaseFirestore.instance.collection('users').orderBy('name'), //Change types accordingly itemBuilderType: PaginateBuilderType.listView, shrinkWrap: false, // to fetch real-time data isLive: true, );

hello .. I love your packages but my project need to tab . when I use this package on NestedScrollView but scroll with SliverAppBar not working . if I fixed that by SliverChildListDelegate or any widget has scroll I have another problem with paginate firestore it's get all document in once . how I fixed that ? thank u ...

Hi,

a really useful feature would be the ability to modify the query, e.g. when the user picks a different sort or where condition.

Right now the paginator sticks to the original query even if you update the query and setState() or use the PaginateRefreshedChangeListener, which makes it impossible to use in more complex scenarios.

I think the empty display shouldn't take full height and be scrollable by default. I am trying to center my empty display widget at the center of the screen but it's not fully centered because it's being wrapped by the libraries' container which has a full screen height along with a scroll widget.

Due to this line in the PaginationCubit file, there are certain cases where the same document is included twice in the list.

emit(PaginationLoaded( documentSnapshots: previousList + newList, hasReachedEnd: newList.isEmpty, ));

Is it possible to have an initial index? For ex. I have a list of docs, but In my application I'm not always starting at 0. The user can actually click a certain object to start the list at any index.

So If I have the itemsPerPage set to 10. and the user clicks the item at index 12. The list scrolls to 12 at first and then bounces back up to 10 because its the documentsLoaded limit. I'm assuming it's due to the bottom loader interfering.

Thanks

Hi, any plan to support cache query ? as you know we cannot imagine usage of firestore without caching for most of use case, just close and open the app will trigger new docs read if no local cache configured

Can we control the limit of items per page? if so, how?

How to know when is fetching more documents, like a bool variable, to show some CircularProgressIndicator with "loading more data" to the user?

Here is a class you can use that I set up to test the issue that I'm talking about. The initialPage in the initState simulates if someone was clicking the index of 15. Note the itemsPerPage is less at only 10.

class ProfileFeed extends StatefulWidget {
  @override
  _ProfileFeedState createState() => _ProfileFeedState();
}

class _ProfileFeedState extends State<ProfileFeed> {
  late PreloadPageController pageController;
  late DocumentSnapshot initialDocument;
  @override
  void initState() {
    //Here's where you can mess with the initial page to see the problem
    pageController = PreloadPageController(initialPage: 15);
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    return PaginateFirestore(
      itemsPerPage: 10,
      onLoaded: (PaginationLoaded) {},
      itemBuilderType: PaginateBuilderType.pageView,
      pageController: pageController,
      emptyDisplay: const Center(child: Text('No posts..')),
      onError: (dynamic error) => Center(
        child: Text('Some error occured'),
      ),
      bottomLoader: Center(
        // optional
        child: CircularProgressIndicator(),
      ),
      itemBuilder: (
        index,
        context,
        documentSnapshot,
      ) {
        return Container(
          width: MediaQuery.of(context).size.width,
          height: MediaQuery.of(context).size.width,
          child: Center(
            child: Text(
              index.toString(),
              style: TextStyle(fontSize: 50),
            ),
          ),
        );
      },
      // orderBy is compulsary to enable pagination
      query: FirebaseFirestore.instance
          .collection('posts')
          .orderBy('dateAdded', descending: true),
    );
  }
}

Listener example is not working I am receiving syntax errors in Android Studio and will it be able to update whenever a collection changes with pulling a loader

Hi I am using this package in a project of mine which shows realtime feeds and allows users to like/comment. Whenever I am using the package to pull data in Live mode everything works fine. But whenever there is new data added to the firestore, the listview position scrolls on its own due to the new data added on top. This is because my query fetches data ordered in descending order.

Any idea how this can be resolved?

Hi, I've been using this package for quite a while. And recently, a new feature from Firestore just got launched, which is count(). I wanted to use that feature, but the problem is, I have to upgrade my cloud_firestore package to the latest version, which paginate_firestore doesn't support and results in a version conflict. Is there any chance you can make it so that paginate_firestore is compatible with cloud_firestore's latest version? Or can I do it by myself by forking the package? Any help would be greatly appreciated.

First of all this package is very handy and I use it in several projects, so I appreciate it.

My intention is to load 5 new documents each time user swipes the first 5 documents, so I have this attribute on my widget itemsPerPage: 5,. But my main goal is to restrict some users the maximum amount of documents they can load. Like in a query you would normally use in a FutureBuilder;

child: FutureBuilder<QuerySnapshot>(
          future: FirebaseFirestore.instance
              .collection('Upcoming')
              .orderBy('ReleaseTimestamp')
              .where('ReleaseTimestamp', isGreaterThan: Timestamp.now())
              .limit(3) // This actually only loads 3 documents totally
              .get(),

But when trying to do the exact same procedure with this package the limit method used in the query is ignored;

class ExampleWidget extends StatelessWidget {
  const ExampleWidget ({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return PaginateFirestore(
      pageController: PageController(viewportFraction: 0.85),
      scrollDirection: Axis.horizontal,
      itemsPerPage: 5,
      itemBuilderType: PaginateBuilderType.pageView,
      query: FirebaseFirestore.instance
          .collection('Menu')
          .orderBy('Timestamp', descending: true)
          .limit(10), // ! THIS DOESN'T WORK
      itemBuilder: (context, snapshot, index) {
        return Text(snapshot.toString());
      },
    );
  }
}

Any idea how can I limit the total queried documents while also using the pagination? Like I want some users to load max 100 documents but paginate these 100 documents 20 by 20.

Is it possible to not just limit the number of items per page but limit the total number of items or the number pages. For example, i only want for some cases to display 3 items and stop the pagination no matter how many items are left in the collection. Is this behavior possible?

Thank you.