Remove "for an external resource" from the definition of handleFetch - #6713
Merged
Conversation
|
for an external URL from the definition of handleFetchhandleFetch
dummdidumm
approved these changes
Sep 12, 2022
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
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.
#6565 replaced the
externalFetchhook with a more generichandleFetchwhich isn't specific to requests with external URLs. I think this part of the documentation wasn't updated to reflect that, it should no longer say "...for an external resource..." in the definition of thehandleFetchhook.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
Changesets
pnpm changesetand following the prompts. All changesets should bepatchuntil SvelteKit 1.0