Make element returned by useOutlet have stable-ish reference #13382
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.
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
useOutlet
wraps 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
children
prop.I'm not sure we can guarantee stable references from
useOutlet
going forward, but that would be nice.