Book Image

State Management with React Query

By : Daniel Afonso
Book Image

State Management with React Query

By: Daniel Afonso

Overview of this book

State management, a crucial aspect of the React ecosystem, has gained significant attention in recent times. While React offers various libraries and tools to handle state, each with different approaches and perspectives, one thing is clear: state management solutions for handling client state are not optimized for dealing with server state. React Query was created to address this issue of managing your server state, and this guide will equip you with the knowledge and skills needed to effectively use React Query for state management. Starting with a brief history of state management in the React ecosystem, you’ll find out what prompted the split from a global state to client and server state and thus understand the need for React Query. As you progress through the chapters, you'll see how React Query enables you to perform server state tasks such as fetching, caching, updating, and synchronizing your data with the server. But that’s not all; once you’ve mastered React Query, you’ll be able to apply this knowledge to handle server state with server-side rendering frameworks as well. You’ll also work with patterns to test your code by leveraging the testing library and Mock Service Worker. By the end of this book, you'll have gained a new perspective of state and be able to leverage React Query to overcome the obstacles associated with server state.
Table of Contents (14 chapters)
Part 1: Understanding State and Getting to Know React Query
Part 2: Managing Server State with React Query

Creating infinite queries

Another very common UI pattern is building an infinite scroll component. In this pattern, we are presented with a list that allows us to load more data as we scroll down.

To deal with these types of lists, React Query has an alternative to the useQuery hook, which is another custom hook called useInfiniteQuery.

Using the useInfiniteQuery hook has many similarities to the useQuery one, but some things differ that we need to be aware of:

  • Your data is now an object that contains the following:
    • The fetched pages
    • The page parameters that were used to fetch the pages
  • A function called fetchNextPage to fetch the next page
  • A function called fetchPreviousPage to fetch the previous page
  • A Boolean state called isFetchingNextPage to indicate that the next page is being fetched
  • A Boolean state called isFetchingPreviousPage to indicate that the next page is being fetched
  • A Boolean state called hasNextPage to indicate whether the list has...