I've been intrigued by the idea of migrating our server data state management from Redux to React-Query, as it purports to take a lot of the boilerplate out of managing data fetched from an API. (Specifically, it focuses on the idea of differentiating between "client" state and "server" or "data" state - see https://react-query.tanstack.com/guides/does-this-replace-client-state for more info.)
Currently this codebase has a lot of duplicate boilerplate for Redux Saga-related actions and I'm curious whether we could use this to slim down the infrastructure side of the app.
I'll be looking into this soon (hopefully) but anyone who wants to help do research on it or fire up a proof of concept is welcome to take a crack at it!
I've been intrigued by the idea of migrating our server data state management from Redux to React-Query, as it purports to take a lot of the boilerplate out of managing data fetched from an API. (Specifically, it focuses on the idea of differentiating between "client" state and "server" or "data" state - see https://react-query.tanstack.com/guides/does-this-replace-client-state for more info.)
Currently this codebase has a lot of duplicate boilerplate for Redux Saga-related actions and I'm curious whether we could use this to slim down the infrastructure side of the app.
I'll be looking into this soon (hopefully) but anyone who wants to help do research on it or fire up a proof of concept is welcome to take a crack at it!