-
Notifications
You must be signed in to change notification settings - Fork 27.2k
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 incorrect refresh request when basePath is set #64589
Merged
ztanner
merged 1 commit into
canary
from
04-16-fix_incorrect_refresh_request_when_basePath_is_set
Apr 17, 2024
Merged
fix incorrect refresh request when basePath is set #64589
ztanner
merged 1 commit into
canary
from
04-16-fix_incorrect_refresh_request_when_basePath_is_set
Apr 17, 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
ijjk
added
area: tests
created-by: Next.js team
PRs by the Next.js team.
type: next
labels
Apr 16, 2024
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Tests Passed |
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
build cache
Diff detailsDiff for middleware.jsDiff too large to display Diff for 2453-HASH.jsDiff too large to display |
ztanner
requested review from
timneutkens,
ijjk,
shuding,
huozhi,
feedthejim and
wyattjoh
as code owners
April 17, 2024 00:21
ijjk
approved these changes
Apr 17, 2024
ztanner
deleted the
04-16-fix_incorrect_refresh_request_when_basePath_is_set
branch
April 17, 2024 01:01
ztanner
added a commit
that referenced
this pull request
Apr 17, 2024
`initialCanonicalUrl` differs from the `canonicalUrl` that gets set on the client, such as when there's a basePath set. This hoists the `canonicalUrl` construction up so we can re-use it when adding refetch markers to the tree. This also renames `pathname` -> `path` since it also includes search params. I added a test to confirm no extra erroneous fetches happened in both cases. Fixes #64584 Closes NEXT-3130
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.
initialCanonicalUrl
differs from thecanonicalUrl
that gets set on the client, such as when there's a basePath set.This hoists the
canonicalUrl
construction up so we can re-use it when adding refetch markers to the tree.This also renames
pathname
->path
since it also includes search params. I added a test to confirm no extra erroneous fetches happened in both cases.Fixes #64584
Closes NEXT-3130