Summary
Migrate the Redux layer to modern patterns in a single consolidated effort, since these changes are tightly coupled.
Scope
-
Redux Toolkit migration — Convert all reducers (configurations, settings, log, connectionState, monkeyID, tabs) to RTK slices with createSlice. Replace the manual combineReducers + createStore setup with configureStore.
-
Class → functional components — Convert ~10 class components to functional components with hooks. Each needs careful state and lifecycle migration (componentDidMount → useEffect, etc.).
-
Replace connect() with Redux hooks — Swap mapStateToProps/mapDispatchToProps + connect() HOCs for useSelector/useDispatch in all connected components.
Why consolidated
RTK slices change action creators and reducer shapes, which forces updates in connected components. Converting those components to functional at the same time avoids doing two passes over the same files. Once functional, connect() → hooks is a natural follow-up within the same PR.
Sequencing suggestion
- Start with leaf reducers (e.g.,
log, tabs) and their connected components
- Work inward to
configurations and settings (most complex)
- Update tests as each reducer migrates
Summary
Migrate the Redux layer to modern patterns in a single consolidated effort, since these changes are tightly coupled.
Scope
Redux Toolkit migration — Convert all reducers (
configurations,settings,log,connectionState,monkeyID,tabs) to RTK slices withcreateSlice. Replace the manualcombineReducers+createStoresetup withconfigureStore.Class → functional components — Convert ~10 class components to functional components with hooks. Each needs careful state and lifecycle migration (
componentDidMount→useEffect, etc.).Replace
connect()with Redux hooks — SwapmapStateToProps/mapDispatchToProps+connect()HOCs foruseSelector/useDispatchin all connected components.Why consolidated
RTK slices change action creators and reducer shapes, which forces updates in connected components. Converting those components to functional at the same time avoids doing two passes over the same files. Once functional,
connect()→ hooks is a natural follow-up within the same PR.Sequencing suggestion
log,tabs) and their connected componentsconfigurationsandsettings(most complex)