-
Notifications
You must be signed in to change notification settings - Fork 27.6k
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 navigation issue when dynamic param casing changes #61726
Merged
ztanner
merged 1 commit into
canary
from
02-06-fix_navigation_issue_when_dynamic_param_casing_changes
Feb 6, 2024
Merged
fix navigation issue when dynamic param casing changes #61726
ztanner
merged 1 commit into
canary
from
02-06-fix_navigation_issue_when_dynamic_param_casing_changes
Feb 6, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This stack of pull requests is managed by Graphite. Learn more about stacking. |
ztanner
force-pushed
the
02-06-fix_navigation_issue_when_dynamic_param_casing_changes
branch
from
February 6, 2024 16:32
145d7d0
to
7ee2016
Compare
ztanner
force-pushed
the
02-06-fix_navigation_issue_when_dynamic_param_casing_changes
branch
from
February 6, 2024 16:33
7ee2016
to
ce2adfc
Compare
Stats from current PRDefault BuildGeneral
Client Bundles (main, webpack)
Legacy Client Bundles (polyfills)
Client Pages
Client Build Manifests
Rendered Page Sizes
Edge SSR bundle Size
Middleware size
Next Runtimes
Diff detailsDiff for page.jsDiff too large to display Diff for 68-HASH.jsDiff too large to display |
ztanner
requested review from
timneutkens,
ijjk,
shuding,
huozhi,
feedthejim and
wyattjoh
as code owners
February 6, 2024 16:54
ijjk
approved these changes
Feb 6, 2024
ztanner
deleted the
02-06-fix_navigation_issue_when_dynamic_param_casing_changes
branch
February 6, 2024 16:59
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What
When navigating to a page with dynamic params using a certain casing, and then following a link to another page using different casing for the same param, the router would get stuck in an infinite suspense cycle.
Why
On the client we normalize cache keys by lowercasing the values for dynamic segments. However the RSC data for each segment wouldn't have this same casing logic applied. This is causing the router to not recognize that there is already RSC data available for that segment, resulting in an infinite suspense cycle.
How
The
toLowerCase()
logic shouldn't be needed here. Technically we could leave this in place and updatematchSegment
to also apply the lowercase logic, but currently there are too many utility functions that parse segments to comfortably make that change. I confirmed that the bug related to why we lowercased these router cache keys is no longer present after making this change.Fixes #61722
Closes NEXT-2377