FWIW, I want to apologize a bit, because it sounds like A) you were being required to use Redux on a project that probably didn't actually need it, and B) while you can put literally any kind of state into the Redux store, we generally recommend that most form state shouldn't go in Redux. So, those probably made it a bit harder, on top of trying to learn just what Redux is and how it works in the first place.
Out of curiosity, what resources were you using to learn Redux? We're starting a major rewrite of the Redux core docs, and I'd appreciate any feedback you could offer on what specific problems you had while trying to learn it (difficult terms, concepts that didn't make sense, what explanations finally made things click, etc).
Also, please check out our new official Redux Starter Kit package. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once:
Congrats on finishing that!
FWIW, I want to apologize a bit, because it sounds like A) you were being required to use Redux on a project that probably didn't actually need it, and B) while you can put literally any kind of state into the Redux store, we generally recommend that most form state shouldn't go in Redux. So, those probably made it a bit harder, on top of trying to learn just what Redux is and how it works in the first place.
Out of curiosity, what resources were you using to learn Redux? We're starting a major rewrite of the Redux core docs, and I'd appreciate any feedback you could offer on what specific problems you had while trying to learn it (difficult terms, concepts that didn't make sense, what explanations finally made things click, etc).
Also, please check out our new official Redux Starter Kit package. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once:
redux-starter-kit.js.org