Describe combining useContext and useReducer for scalable feature state
This tests replacing prop drilling with a context-reducer pattern. A strong answer covers two contexts for state and dispatch, a provider wrapping the subtree, and a pure reducer. A red flag is one global context or async logic inside the reducer.
This tests whether you can build self-contained feature state without prop drilling. A strong answer explains creating separate contexts for state and dispatch to avoid unnecessary re-renders, wrapping the feature subtree in a provider that owns the useReducer call, keeping the reducer pure and deterministic, and defining typed dispatch actions. A red flag is advocating a single global app context, putting side effects inside the reducer, or failing to split state and dispatch contexts which forces every consumer to re-render on any change.
Read the original → react.dev
- #react
- #state-management
- #usecontext
- #usereducer
- #advanced
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.