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)
1
Part 1: Understanding State and Getting to Know React Query
5
Part 2: Managing Server State with React Query

Renaming cacheTime to gcTime

This was one of the changes I’m most personally happy about because it is probably the most misunderstood option in React Query. Most often, it is assumed that cacheTime means the length of time that data will be cached instead of what it really means, which is the time that inactive data in the cache will remain in memory.

To stop this misconception, the cacheTime option has been renamed gcTime. This is because gc is often a shortened way to refer to the garbage collector. Therefore, from now on, we explicitly declare the time until our data is garbage-collected.

To use it, all you need to do is add the gcTime option to your useQuery/useMutation hook, like this:

useQuery({
    gcTime: 60000
});

In the snippet, we define that after our query is inactive for one minute, the data will be garbage-collected.

To wrap up the renaming spree, let us see how our Hydrate component changed.