Making fetch useful in more and more React scenario's will however become more complex over time. This video about react-query shows what I mean: youtube.com/watch?v=seU46c6Jz7E
I'm not saying you should use react-query and I encourage people to write things themselves before they grab a library. But it's nice to have an option in the back of your head when you reach the point where you are saying to yourself: "ouch, this is becoming too complex".
Thanks for the feedback! I know react-query and I agree with you that it's more suitable in complex web apps. That's what I wrote just before the "Connect" title 😊, maybe you missed it.
In complex web apps, making a lot of network requests, requiring advanced features like caching, it will probably be better to use React Query, a powerful React data synchronization library.
Maybe I should have talked more about React Query because it is a very powerful library, as you said. Thanks to your comment, this tip has gotten the space it deserves 😃.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Great tutorial!
Making
fetchuseful in more and more React scenario's will however become more complex over time. This video aboutreact-queryshows what I mean: youtube.com/watch?v=seU46c6Jz7EI'm not saying you should use
react-queryand I encourage people to write things themselves before they grab a library. But it's nice to have an option in the back of your head when you reach the point where you are saying to yourself: "ouch, this is becoming too complex".Thanks for the feedback! I know
react-queryand I agree with you that it's more suitable in complex web apps. That's what I wrote just before the "Connect" title 😊, maybe you missed it.Ahh yeah, I must have skipped over it.
Maybe I should have talked more about React Query because it is a very powerful library, as you said. Thanks to your comment, this tip has gotten the space it deserves 😃.