-
-
Notifications
You must be signed in to change notification settings - Fork 10.7k
Make element returned by useOutlet have stable-ish reference #13382
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
Conversation
🦋 Changeset detectedLatest commit: dab6471 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 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 |
|
Hi @Malien, Welcome, and thank you for contributing to React Router! Before we consider your pull request, we ask that you sign our Contributor License Agreement (CLA). We require this only once. You may review the CLA and sign it by adding your name to contributors.yml. Once the CLA is signed, the If you have already signed the CLA and received this response in error, or if you have any questions, please contact us at [email protected]. Thanks! - The Remix team |
|
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
|
Could you add a changeset for this? |
|
@brophdawg11 Yeah. I did. Sorry for the late change |
|
🤖 Hello there, We just published version Thanks! |
|
🤖 Hello there, We just published version Thanks! |
I was trying to accomplish an exit animation for routes rendered in
<Outlet />s. I need to hold onto the previous value of outlet until it finishes its animation.Calling setState in render is THE way to capture the previous value. Reading refs in render isn't really allowed.
Since
useOutletwraps the<RenderedRoute />in<OutletContext.Provider />, the reference to the outer<OutletContext.Provider />is always different on every re-render. And the code above triggers an infinite render loop.This PR just wraps the resulting element in
useMemo. That's it.The workaround for me currently involves asserting that the element is in fact the react context, and grabbing the stable
childrenprop.I'm not sure we can guarantee stable references from
useOutletgoing forward, but that would be nice.