You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Victor & I spoke about this briefly today. Having types flow through is really nice (e.g. #1710) however the work involved in moving from (non-trivial) class-components to hooks shouldn't be underestimated. Changing to createSlice looks to be a similar amount of work, and my intuition is that having a codebase using a mixture of createSlice and our current (and previously recommended) approach will be hard to reason with.
I tried porting the tree reducers to createSlice briefly while working on #1864. Didn't get very far (6924553), but my impression is that it's not easy or maybe even impossible to have a mixed codebase.
Redux was adopted in Auspice many years ago. Since then, Redux has developed new features to simplify usage (e.g. Redux Toolkit, hooks API).
Steps from the migration guide (doesn't have to be followed in order):
configureStore
: eb2c30fcreateSlice
createAsyncThunk
createListenerMiddleware
connect
to HooksThe text was updated successfully, but these errors were encountered: