-
Notifications
You must be signed in to change notification settings - Fork 2.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
Throw single fetch redirects fetched from the server #10317
Conversation
🦋 Changeset detectedLatest commit: 29cb306 The changes in this PR will be included in the next version bump. This PR includes changesets to release 19 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 |
@@ -491,7 +491,7 @@ function unwrapSingleFetchResult(result: SingleFetchResult, routeId: string) { | |||
if (result.replace) { | |||
headers["X-Remix-Replace"] = "yes"; | |||
} | |||
return redirect(result.redirect, { status: result.status, headers }); | |||
throw redirect(result.redirect, { status: result.status, headers }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❤️ |
🤖 Hello there, We just published version Thanks! |
🤖 Hello there, We just published version Thanks! |
Align the logic with non-Single Fetch to always throw redirects from the client loader so short circuit any further processing and avoid type inference mismatches
Closes #10208