Pagination with React.js and Firebase Firestore

In this article, we learn how to paginate data fetched from Firebase Firestore with React.js

·6 min read
Cover Image for Pagination with React.js and Firebase Firestore

👋 Hi! Would you like to learn how to build an AI SaaS with Next.js, Supabase and Stripe including a fully working SaaS template? Check out our new course!

Using pagination with Firebase Firestore and React.js is not as simple as it looks; I know, as it's given me more than a headache.

Unfortunately, Firestore has an important limitation: in fact, we cannot paginate data using numerical indexes.

For example, we cannot make a query that takes our data from index 20 to index 40. Instead, our starting point will need to be a document snapshot: this makes it impossible to paginate data by a specific page, but, instead, we can opt for a sequential pagination.

In this article, I want to show you the simplest way to paginate your Firestore data in a table, with the possibility of going back and forth between pages.

Many of the examples below will use Makerkit's components: these are simple implementation details, so just ignore them if you're not using Makerkit.

The final result will look like the image below:

Writing Paginated queries with Firestore

Let's assume that we want to make a query to the tasks collection by a couple of parameters:

  1. we will query the tasks that have an organizationId property that matches the argument organizationId
  2. we will paginate them ordered by the property dueDate
  3. we will use two parameters to control the pagination: cursor and itemsPerPage
useFetchTasks.ts
import { useFirestore, useFirestoreCollection } from 'reactfire';
 
import {
  collection,
  CollectionReference,
  limit,
  orderBy,
  startAfter,
  query,
  where,
  DocumentSnapshot,
} from 'firebase/firestore';
 
import { Task } from '~/lib/tasks/types/task';
 
function useFetchTasks(
  organizationId: string,
  params: {
    cursor: Maybe<DocumentSnapshot>;
    itemsPerPage: number;
  }
) {
  const firestore = useFirestore();
 
  // collection path
  const tasksCollection = 'tasks';
 
  // we order tasks by the "dueDate" property
  const order = orderBy('dueDate', 'desc');
 
  const path = `organizationId`;
  const operator = '==';
 
  // create default constraints
  const constraints = [
    where(path, operator, organizationId),
    order,
    limit(params.itemsPerPage),
  ];
 
  // if cursor is not undefined (e.g. not initial query)
  // we pass it as a constraint
  if (params.cursor) {
    constraints.push(
      startAfter(params.cursor)
    );
  }
 
  const collectionRef = collection(
    firestore,
    tasksCollection
  ) as CollectionReference<WithId<Task>>;
 
  const organizationsQuery = query(collectionRef, ...constraints);
 
  return useFirestoreCollection(organizationsQuery, {
    idField: 'id',
  });
}
 
export default useFetchTasks;

We are going to use the custom hook above to fetch data from the tasks collection. But first, let's create a new custom hook: useFetchTasksCount.

Counting the documents of a Firestore Collection

As of October 2022, this feature has just been released by Firebase: counting how many documents are in a Firestore collection.

Thanks to this new functionality, we will know if we can continue paginating our documents generally, it's also a good UX practice to show how many documents the user can scroll through.

To count the total number of documents in a Firestore collection we are going to use the function getCountFromServer: this function accepts a Firestore query and will return the number of documents found according to the query.

In our case, we want to collect the total count of tasks given the organizationId passed as parameter.

useFetchTasksCount.ts
import { useCallback } from 'react';
import { useFirestore } from 'reactfire';
 
import {
  where,
  getCountFromServer,
  query,
  collection,
  CollectionReference,
} from 'firebase/firestore';
 
import { Task } from '~/lib/tasks/types/task';
 
const tasksCollection = 'tasks';
const path = `organizationId`;
const operator = '==';
 
function useFetchTasksCount() {
  const firestore = useFirestore();
 
  return useCallback(
    (organizationId: string) => {
      const constraints = [where(path, operator, organizationId)];
 
      const collectionRef = collection(
        firestore,
        tasksCollection
      ) as CollectionReference<WithId<Task>>;
 
      return getCountFromServer(
        query(collectionRef, ...constraints)
      );
    },
    [firestore]
  );
}
 
export default useFetchTasksCount;

Paginated Table with Firestore and React.js

Now, we can finally use our custom hooks to fetch data from our Firestore collections and display it in a simple table.

We create two components: a table named TasksTable and a pagination component named Pagination.

  1. The table component is responsible for fetching and displaying the data
  2. The pagination component will render the buttons to go back and forth, and will notify the table component when the page is changed

We're going to use one single state property for handling re-renderings: the page state. When this property changes (using the user's input), the component will update the cursor and fetch the new data.

TasksTable.tsx
const itemsPerPage = 4;
 
const TasksTable: React.FC<{
  organizationId: string;
}> = ({ organizationId }) => {
  const [page, setPage] = useState(0);
 
  // keep cursors in memory
  const cursors = useRef<Map<number, DocumentSnapshot>>(new Map());
 
  // use query fetching
  const { data, status } = useFetchTasks(organizationId, {
    cursor: cursors.current.get(page),
    itemsPerPage,
  });
 
  // collect all the tasks JSON data
  const tasks = useMemo(() => {
    return data?.docs?.map((doc) => doc.data()) ?? [];
  }, [data]);
 
  // callback called when changing page
  const onPageChanged = useCallback(
    (nextPage: number) => {
      setPage((page) => {
        // first, we save the last document as page's cursor
        cursors.current.set(
          page + 1,
          data.docs[data.docs.length - 1]
        );
 
        // then we update the state with the next page's number
        return nextPage;
      });
    },
    [data]
  );
 
  if (status === `loading`) {
    return <span>Loading Tasks...</span>;
  }
 
  return (
    <div className={'flex flex-col space-y-2'}>
      <table className={'Table'}>
        <thead>
          <tr>
            <th>Name</th>
            <th>Due Date</th>
            <th>Done</th>
          </tr>
        </thead>
 
        <tbody>
          {tasks.map((task) => {
            return (
              <tr key={task.name}>
                <td>{task.name}</td>
                <td>{task.dueDate}</td>
                <td>{task.done ? `Done` : `Not done`}</td>
              </tr>
            );
          })}
        </tbody>
      </table>
 
      <Pagination
        currentPage={page}
        organizationId={organizationId}
        pageChanged={onPageChanged}
      />
    </div>
  );
};
 
export default TasksTable;

Let's explain the above.

We keep two stateful constants: page and cursors.

  1. page represents the current page. Only the page state will trigger re-renderings.
  2. cursors represents a map page->cursor. We need the cursor because we use it to retrieve the tasks of a certain page. To prevent re-renderings, cursors is a reference.
const [page, setPage] = useState(0);
 
// keep cursors in memory
const cursors = useRef<Map<number, DocumentSnapshot>>(new Map());

Then, we use the custom React hook above to fetch the paginated data from Firestore.

As you can see below, we pass the page's cursor based on the page state:

// use query fetching
const { data, status } = useFetchTasks(organizationId, {
  cursor: cursors.current.get(page),
  itemsPerPage,
});
 
// collect all the tasks JSON data
const tasks = useMemo(() => {
  return data?.docs?.map((doc) => doc.data()) ?? [];
}, [data]);

Finally, we listen to the Pagination component's callback that will notify us when the user changes page.

Of course, we set the page state to the new page. It's also important to notice that it's in this callback that we set the cursors for the current page. In this way, we avoid re-renderings. When the component re-renders, it will pick up the correct cursor for the current page.

// callback called when changing page
const onPageChanged = useCallback(
  (nextPage: number) => {
    setPage((page) => {
      // first, we save the last document as page's cursor
      cursors.current.set(
        page + 1,
        data.docs[data.docs.length - 1]
      );
 
      // then we update the state with the next page's number
      return nextPage;
    });
  },
  [data]
);

Now, let's take a look at the pagination component:

function Pagination(
  props: React.PropsWithChildren<{
    organizationId: string;
    currentPage: number;
    pageChanged: (page: number) => unknown;
  }>
) {
  const fetchTaskCount = useFetchTasksCount();
  const [tasksCount, setTasksCount] = useState<number>();
 
  useEffect(() => {
    // when the component mounts, we store the tasks count in the state
    fetchTaskCount(props.organizationId).then((result) => {
      setTasksCount(result.data().count);
    });
  }, [fetchTaskCount, props.organizationId]);
 
  if (tasksCount === undefined) {
    return <div>Loading...</div>;
  }
 
  const totalPages = Math.floor(tasksCount / itemsPerPage);
  const canGoBack = props.currentPage >= 1;
  const canGoNext = props.currentPage < totalPages;
 
  return (
    <div className={'flex flex-row justify-end space-x-0.5'}>
      <Button
        color={'transparent'}
        disabled={!canGoBack}
        onClick={() => props.pageChanged(props.currentPage - 1)}
      >
        <span className={'flex items-center space-x-2'}>
          <ChevronLeftIcon className={'h-5'} />
          <span>Previous</span>
        </span>
      </Button>
 
      <Button
        color={'transparent'}
        disabled={!canGoNext}
        onClick={() => props.pageChanged(props.currentPage + 1)}
      >
        <span className={'flex items-center space-x-2'}>
          <span>Next</span>
 
          <ChevronRightIcon className={'h-5'} />
        </span>
      </Button>
    </div>
  );
}

Demo

Below is the final result using the Makerkit's components:

Loading video...

👋 Hi! Would you like to learn how to build an AI SaaS with Next.js, Supabase and Stripe including a fully working SaaS template? Check out our new course!

Read more about Tutorials

Cover Image for Building an AI Writer SaaS with Next.js and Supabase

Building an AI Writer SaaS with Next.js and Supabase

·57 min read
Learn how to build an AI Writer SaaS with Next.js and Supabase - from writing SEO optimized blog posts to managing subscriptions and billing.
Cover Image for Announcing the Data Loader SDK for Supabase

Announcing the Data Loader SDK for Supabase

·8 min read
We're excited to announce the Data Loader SDK for Supabase. It's a declarative, type-safe set of utilities to load data into your Supabase database that you can use in your Next.js or Remix apps.
Cover Image for Adding AI capabilities to your Next.js SaaS with Supabase and HuggingFace

Adding AI capabilities to your Next.js SaaS with Supabase and HuggingFace

·20 min read
In this tutorial, we will learn how to use add AI capabilities to your SaaS using Supabase Vector, HuggingFace models and Next.js Server Components.
Cover Image for Building an AI-powered Blog with Next.js and WordPress

Building an AI-powered Blog with Next.js and WordPress

·17 min read
Learn how to build a blog with Next.js 13 and WordPress and how to leverage AI to generate content.
Cover Image for Using Supabase Vault to store secrets

Using Supabase Vault to store secrets

·6 min read
Supabase Vault is a Postgres extension that allows you to store secrets in your database. This is a great way to store API keys, tokens, and other sensitive information. In this tutorial, we'll use Supabase Vault to store our API keys
Cover Image for Introduction to Next.js Server Actions

Introduction to Next.js Server Actions

·9 min read
Next.js Server Actions are a new feature introduced in Next.js 13 that allows you to run server code without having to create an API endpoint. In this article, we'll learn how to use them.