You cannot call this.setState from the body of this update lifecycle method.

You cannot call this.setState from the body of this update lifecycle method.

• A. ComponentWillUpdate
• B. ComponentWillMount
• C. Render
• D. ComponentDidUpdate

Answer: (A)

In the update path, React is about to re-render with new props or state. Calling this.setState inside the pre-render update hook would schedule another update while React is still handling the current one, which can trigger extra renders and even cause an unstable loop. Because of that, you should not set state from this update-stage method. If you need to react to prop changes, do so in safer places: derive values in a constructor or a static getDerivedStateFromProps (for modern patterns), or perform related actions after the update in componentDidUpdate with proper guards. Note that componentWillUpdate itself is deprecated in newer React versions, with these safer patterns taking its place.

In the update path, React is about to re-render with new props or state. Calling this.setState inside the pre-render update hook would schedule another update while React is still handling the current one, which can trigger extra renders and even cause an unstable loop. Because of that, you should not set state from this update-stage method.

If you need to react to prop changes, do so in safer places: derive values in a constructor or a static getDerivedStateFromProps (for modern patterns), or perform related actions after the update in componentDidUpdate with proper guards. Note that componentWillUpdate itself is deprecated in newer React versions, with these safer patterns taking its place.