@_benjimouse_

I joined a project about 9 months ago, which was deeply into useEffect/Redux hell. The cognitive load to understand what was going on some screens was exhausting. I proposed we use a query manager, and we settled on TansStack. The code we've been writing for new functions is significantly simpler and more "React-y". It's pretty much essential to be using it or something similar imo.

@tashriser

Man, I love this lib! ❤ Great overview, Kyle! Can't get enough of your videos.

Man, please develop a small to mid size project showing how to organize the codebase with React Query alongside a state management library like Zustand.

@masaeedi1

I have just started working with React Query and it has been just an amazing experience.  Still learning to get better at it

@EvertJunior

You're the best teacher on YouTube, your explanations are always clear and fast, thank you so much. What I don't like about solutions like this is all the pop-ins and excessive loading states. For us developers this is nice and efficient but for users it's distracting and overall bad UX. I like the server rendering approach of Next which is fast like static but interactive where needed. React itself seems to be going in that direction with server components. Exciting times for web developers!

@shahbazahmad7233

thanks bro i was stuck in intergrating react query , we are always biggeners to new things and it just fixes all of my problems i have project that only enlisting them took 2 hours

@eduardodrumond8850

This is very similar to Apollo Client, which was built for graphql. So nice to see good ideas spreading it through the community. :)

@MultiSgar

Thanks for this tutorial! It's very clear and concise: I am almost done migrating the front end of my project to react query thanks to you.

@yakovavraham4247

Sounds like using the cache and refetch in the background then update the state when we get a response can lead to a bad UX especially when fetching takes a relatively long time

@tyrellbb

I love TanStack Query too. I used it on a recent project. Well done Kyle. This is an extensive yet succinct overview.

@FarisEjaz-q3h

Great tutorial. Well structured and easy to understand.

@havocthehobbit

so just it's for promise's while wait and error state handling. I would have named it useWaitState or WWS (whileWaitState) , surprised there arnt primitives for this in every framework/library or that promises doesnt have a standard onWaiting member event as part of the js spec, it sounds like a pretty obvious convention to have with a language that uses callbacks and async in alot of it base.

@Aaronmoreno

timing couldn't be more perfect, was just about to move all calls to this

@leonardofernandesperes

I was looking at react query yesterday and you come wit hthat video, thank you mate!

@Tajdev

When we com back to posts list, it should show message that new posts are being refreshed or checked.

@hariramnandagopal3567

Great video. 

A small heads up, that getPost does not need to be a Promise. 

If your use case does not involve asynchronous operation, You can call normal function and still get all the benefits ✌️

You can even use React query as a mini state manager too 😅 so many use cases.

@hakuna_matata_hakuna

Do a genuine comparison between react query and swr , just skimming the swr docs gave me feel like optimistic updates might be better in swr

@badmuskaybee5111

Awesome review

@AlazTetik

Great and helpful again! Thank you Kyle! :trophy-yellow-smiling: :face-red-heart-shape: :hand-pink-waving:

@calvinwilliams729

Ill be very happy if the crash course is ready

@Orenrs

Finally ;) waited for this video! If you can do a video where you can show the different implementation of "with" react-query and "without" so we can see the true advantage