-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 useMatches
returning different loader data on sub navigation on client side
#5556
Conversation
… with `shouldRevalidate` (remix-run#5434)
…-rap-http` to community adapters list (remix-run#5402) Co-authored-by: Michaël De Boey <info@michaeldeboey.be>
🦋 Changeset detectedLatest commit: 5be576f The changes in this PR will be included in the next version bump. This PR includes changesets to release 18 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 @wizardlyhel, Welcome, and thank you for contributing to Remix! 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 hello@remix.run. Thanks! - The Remix team |
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
useMatches
causing client side render twice on sub navigationuseMatches
causing client side returning different loader data on sub navigation
useMatches
causing client side returning different loader data on sub navigationuseMatches
returning different loader data on sub navigation on client side
@wizardlyhel Thanks for this! Would you mind rebasing onto Once updated, I can bring over the new integration tests from #5601 as well and then we can get this merged |
I mess up the rebase recreate the PR #5603 with |
Closes: #
Problem:
useMatches
returning different route match data on sub navigation. This problem isn't obvious because the lastuseMatches
hook call always returns the correct route's loader datahttps://stackblitz.com/edit/remix-run-remix-askr4f?file=app/root.tsx
Navigate between home, test and test 2 page.
useMatches
of the same route (This is fine and it is due to React re-renders)useMatches
but of different route loader data. It is always the current route and the previous routeNotice that the server side console only logs loader data for the correct route