3 ms·

Have you considered including React Query in your overview?

acemarke 6y ago
Yes, I intend the site to have an entire "Data Fetching and Caching" section that would cover things like: - Common tools for making AJAX calls (`fetch`, `axios`, self-written wrappers around `fetch`, and when to use any of those) - Info on things like REST and GraphQL as common backend API types - Libraries like React Query, SWR, Apollo, and Urql as common data fetching abstractions, and their use cases Tanner Linsley, author of React Query, has already said that he's happy to write a page on when it makes sense to use React Query [0] I suppose we'd probably want to end up having info on things like Firebase and Hasura too - maybe those would be better suited for a "Backends" section? Like I said in my sibling comment, right now I'm just trying to kickstart the idea of this site, get it off the ground, and get others in the community involved in making it a reality :) [0] https://twitter.com/tannerlinsley/status/1368600315432468482 https://twitter.com/tannerlinsley/status/1368600315432468482
- DamodarSojka 6y ago
  If you will be including Hasura, please also don't forget postgraphile. - a fan of the project
gpspake 6y ago
Came here for this. When the author made me realize that a lot of our global state is just a client side cache of our server side state and we can apply a longstanding http caching standard (SWR) to manage it, it was as big of an aha moment for me as when I was originally introduced to redux. Speaking of redux, I'm a huge fan but React ships with a useReducer hook now - thanks in no small part, I'm sure, to the author of redux working on the react core team. These days, I'm all about reactQuery + react's native useReducer via the hooks and context api. described beautifully by Kent Dodds here: https://kentcdodds.com/blog/how-to-use-react-context-effectively#typescript--flow https://kentcdodds.com/blog/how-to-use-react-context-effecti... I feel like these state management libraries have largely served their purpose in establishing some agreed upon conventions that are now just baked in to React and other libs.

Yes, I intend the site to have an entire "Data Fetching and Caching" section that would cover things like: - Common tools for making AJAX calls (`fetch`, `axios`, self-written wrappers around `fetch`, and when to use any of those) - Info on things like REST and GraphQL as common backend API types - Libraries like React Query, SWR, Apollo, and Urql as common data fetching abstractions, and their use cases Tanner Linsley, author of React Query, has already said that he's happy to write a page on when it makes sense to use React Query [0] I suppose we'd probably want to end up having info on things like Firebase and Hasura too - maybe those would be better suited for a "Backends" section? Like I said in my sibling comment, right now I'm just trying to kickstart the idea of this site, get it off the ground, and get others in the community involved in making it a reality :) [0] https://twitter.com/tannerlinsley/status/1368600315432468482 https://twitter.com/tannerlinsley/status/1368600315432468482

DamodarSojka 6y ago
If you will be including Hasura, please also don't forget postgraphile. - a fan of the project

gpspake 6y ago

Came here for this. When the author made me realize that a lot of our global state is just a client side cache of our server side state and we can apply a longstanding http caching standard (SWR) to manage it, it was as big of an aha moment for me as when I was originally introduced to redux. Speaking of redux, I'm a huge fan but React ships with a useReducer hook now - thanks in no small part, I'm sure, to the author of redux working on the react core team. These days, I'm all about reactQuery + react's native useReducer via the hooks and context api. described beautifully by Kent Dodds here: https://kentcdodds.com/blog/how-to-use-react-context-effectively#typescript--flow https://kentcdodds.com/blog/how-to-use-react-context-effecti... I feel like these state management libraries have largely served their purpose in establishing some agreed upon conventions that are now just baked in to React and other libs.