-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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.
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
Fix bug with changing fetcher key in a mounted component #11009
Conversation
🦋 Changeset detectedLatest commit: 3639f21 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
96c13c6
to
2acc01b
Compare
packages/react-router-dom/index.tsx
Outdated
React.useEffect(() => { | ||
if (key && key !== "" && key != fetcherKey) { | ||
setFetcherKey(key); | ||
} | ||
}, [key, fetcherKey]); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't we set the state directly in render?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll test that out - I always worry about that based on the "rules of hooks" and what not - but a re-reading of the docs makes it sound like this is a valid use case: https://react.dev/reference/react/useState#storing-information-from-previous-renders
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Closes #11008