What is a recommended approach to reduce re-renders caused by context value changes?

What is a recommended approach to reduce re-renders caused by context value changes?

• A. Split large contexts into smaller ones.
• B. Provide all values in a single context.
• C. Always create a new object for the context value.
• D. Avoid using context for state management.

Answer: (A)

When components consume context, they re-render when the value provided by that context changes. Splitting large contexts into smaller ones lets components subscribe only to the data they truly need, so updates to unrelated parts of the state won’t trigger those components to re-render. This keeps render work localized and reduces unnecessary updates. If you put all values into a single context, any change to any piece of data can change the entire context value, causing all consumers to re-render—even if they only use one piece. Creating a new object for the context value on every render also gives the context a new reference each time, which similarly triggers re-renders across subscribers. While context can be used for state management, that alone doesn’t explain how to minimize re-renders; the key is organizing and memoizing the data so that updates don’t ripple through unrelated parts of the UI.

When components consume context, they re-render when the value provided by that context changes. Splitting large contexts into smaller ones lets components subscribe only to the data they truly need, so updates to unrelated parts of the state won’t trigger those components to re-render. This keeps render work localized and reduces unnecessary updates.

If you put all values into a single context, any change to any piece of data can change the entire context value, causing all consumers to re-render—even if they only use one piece. Creating a new object for the context value on every render also gives the context a new reference each time, which similarly triggers re-renders across subscribers. While context can be used for state management, that alone doesn’t explain how to minimize re-renders; the key is organizing and memoizing the data so that updates don’t ripple through unrelated parts of the UI.