4 ms·
I enjoyed it while I used it but my main issues with it were with the developer experience and how many files the logic was spread across: actions, action const
by chenmike 5y ago
I enjoyed it while I used it but my main issues with it were with the developer experience and how many files the logic was spread across: actions, action constants, reducers, etc. When you have to edit 4 different files just to add a loading flag then I feel like something has gone wrong. If it solves your problems and you’re happy though, no need to let anyone convince you to change!
- hajile 5y agoOn really big frontend apps, redux with 4 files becomes the easiest part of the day. It may be verbose, but it’s the one thing that all the other devs won’t be implementing in some weird, proprietary way.
- chenmike 5y agoRedux vs. jank proprietary solution aren't the only options. For instance, a lot of what people use Redux for is fetching and storing API data, or managing cross-component state. A combination of react-query[1] and React context does the same in a much more developer-friendly (IMO) way. Again, not advocating for anything, just important to know what the options are. [1] https://react-query.tanstack.com https://react-query.tanstack.com
- netvarun 5y agoYou should checkout redux toolkit and it’s sibling rtk query - it solves these problems you mentioned really well and has been a breeze to work on a complex app with multiple people. Also both of these libraries are from the official redux team. Just a really happy user and has helped me tame the state problem.