docs: fix incorrect infinite loop claim in set-state-in-render#8413
Open
justismailmemon wants to merge 1 commit intoreactjs:mainfrom
Open
docs: fix incorrect infinite loop claim in set-state-in-render#8413justismailmemon wants to merge 1 commit intoreactjs:mainfrom
justismailmemon wants to merge 1 commit intoreactjs:mainfrom
Conversation
Size changesDetails📦 Next.js Bundle Analysis for react-devThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This updates the explanation in the
set-state-in-renderlint documentation.Problem
The current documentation states that exceeding
maxwill trigger an infinite loop:However, in this specific example, the component stabilizes after an extra render because the condition becomes false once
countis set tomax.Fix
This PR updates the wording to clarify that:
setStateduring renderNotes
The example code is unchanged, as it still correctly demonstrates the anti-pattern.
Closes #8411