Skip to content
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

Bug report: Single fetch: Throwing a response stub with a 3xx status from a resource route results in an unexpected server error #9479

Closed

Conversation

haines
Copy link
Contributor

@haines haines commented May 22, 2024

We had a couple of routes that were only there to redirect to another page in the application, and I forgot to put a default export in the modules.

We discovered that for these routes, the redirect works for data requests, but not for document requests.

I'm guessing this may just be the same problem as in #9471, but it manifests differently (presumably because without a default export it's not treated as a UI route). Instead of a turbo-stream error, the response stub propagates all the way to returnLastResortErrorResponse and we get the plaintext 500 Unexpected Server Error page.

Copy link

changeset-bot bot commented May 22, 2024

⚠️ No Changeset found

Latest commit: 5cf4966

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@brophdawg11
Copy link
Contributor

Thank you for the bug report! This is handled by #9488

@brophdawg11
Copy link
Contributor

And also has some additional test cases added in #9501

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants