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


In this chapter, we learned about all the changes v5 might bring to React Query. By now, you should know about the support changes you will need to be aware of in your browser and understand why we’ve always followed the object format throughout the book.

You’ve seen why logger was removed and understand why renaming loading to pending makes more sense.

Speaking of renaming, you won’t be confused again because gcTime is a more accurate word than cacheTime, and HydrationBoundary represents better what it does than Hydrate.

You’ve learned that for paginated queries, the placeholderData option is the way to go and that keepPreviousData was removed.

Finally, you were introduced to a new way to perform optimistic updates without updating your cache and found a way to save memory in your infinite queries, by leveraging the maxPages option.

As you may recall from what I said previously, this was tested in an alpha version of React Query...