Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying State Management with React Query
  • Table Of Contents Toc
  • Feedback & Rating feedback
State Management with React Query

State Management with React Query

By : Daniel Afonso
5 (5)
close
close
State Management with React Query

State Management with React Query

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

Removing the logger

Previously, React Query logged failed queries to the console in the production environment. This quickly became an issue because our application users could see implementation detail errors that they shouldn’t be aware of. To deal with this issue, the ability to create a custom logger was added, where you could override what React Query used for logging.

Recently, React Query removed all logging in production and improved their development logs. Given this scenario, in v5, logger was no longer needed and was removed.

From now on, console will be used as the default logger.

Now that you know this change, let's see the first renaming of v5 – loading to pending.

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY