fix: Address bugs in SvelteKit “Preloading” tutorial example #1334
Conversation
This file contains hidden or 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
Correctly capture the previous navigation state.
|
@BioniCosmos is attempting to deploy a commit to the Svelte Team on Vercel. A member of the Team first needs to authorize it. |
eltigerchino
added
docs (content)
docs (functionality)
and removed
docs (content)
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes an issue in the SvelteKit “preloading” tutorial where the
previousnavigation details were lost after navigation. This occurred becausepreviousdirectly referenced the mutablenavigatingobject, causing it to update whennavigatingbecamenull.The fix ensures
previousholds a snapshot of the navigation state at its inception by creating a shallow copy ({ ...navigating }) instead of a direct reference.