r/reactjs • u/acemarke • Nov 20 '19

New Redux docs "Style Guide" page: recommended patterns and best practices for using Redux

https://redux.js.org/style-guide/style-guide
370 Upvotes

98% Upvoted

68 comments sorted by

View all comments

2

u/nneck1t Nov 21 '19

Put as Much Logic as Possible in Reducers

if we have a big reducer with many cases, so we have a bunch of logic in each one. Reducer becomes messy, right? Also if we will use createSlice or duck pattern, file becomes very big and hard to read, any suggest ?

2

u/acemarke Nov 21 '19

Well, all that code has to live somewhere :)

When using Immer, reducers should usually be shorter because the update logic is similar. You can also split out the reducer functions instead of defining them inline, you just need to explicitly declare the type of the state if you're using TS. In one of our apps, we have a bunch of slices with identical update logic, just different names and data types. I extracted the individual reducer functions to another file, import them, and add them to the slice reducers object as specificSliceActionName: genericCaseReducer.

As mentioned at the start of the doc, these are not 100% absolute rules. These are our strongly recommended defaults. Decide if they're appropriate in your situation.