redux-selector-rules

Fix Redux selector unnecessary re-renders by ensuring input selectors return primitive values and moving transformations to result functions. This prevents returning new object references on every call, which triggers wasted computations and render loops in React apps.

Your useSelector hook returns new object references because transformations are likely placed in input selectors instead of result functions. Move data transformations to result functions and ensure input selectors return primitives to prevent unnecessary re-renders.

Structure createSelector by splitting logic so input selectors return primitive values and result functions derive data. This input versus result selector discipline ensures memoization works correctly and prevents performance bottlenecks across your React-Redux app.

Yes, these selector rules apply to useSelector and useAppSelector calls in React-Redux apps. Enforcing input-selector discipline and avoiding default values in selectors prevents unnecessary re-renders across the codebase.

Debug Redux selector performance bottlenecks by auditing your selectors to verify input selectors return primitives. Apply migration guidance to identify and fix performance issues by moving transformations to result functions and avoiding default values in selectors.