Skip to content

docs: correct inaccurate infinite loop claim in set-state-in-render #8412

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Assamee wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: correct inaccurate infinite loop claim in set-state-in-render #8412

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
docs: correct inaccurate infinite loop claim in set-state-in-render
  • Loading branch information
@Assamee
Assamee committed Apr 17, 2026
commit e6d52111750a5fd04954bc28a8354b99bb3f4e15
2 changes: 1 addition & 1 deletion src/content/reference/eslint-plugin-react-hooks/lints/set-state-in-render.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ function Counter({max}) {
}
```

As soon as `count` exceeds `max`, an infinite loop is triggered.
Although this won't cause an infinite loop (since the condition eventually becomes false), it interrupts the current render and forces React to start over, making your component slower.

Instead, it's often better to move this logic to the event (the place where the state is first set). For example, you can enforce the maximum at the moment you update state:

Expand Down
Loading