-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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/error redirect #2127
Fix/error redirect #2127
Conversation
🦋 Changeset detectedLatest commit: 7c39318 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
4e54c13
to
fc3892e
Compare
I'm trying to handle the "edgy" case, which is client redirection on It happens here: kit/packages/kit/src/runtime/client/renderer.js Lines 191 to 196 in c3ca3fb
But in the end, i don't believe this is a "real" case in this PR, since by that point, the node is already loaded correctly with the work done in the previous commits. |
yeah, it looks like you've probably covered all the cases. basically just need to rebase and add tests at this point |
1d04bc3
to
ad62940
Compare
I'm struggling with writing the most simple test :/ The nested Am i missing something ? |
Actually, #1576 is the reason why my |
06e26a5
to
c083b2a
Compare
c083b2a
to
7f809c2
Compare
bd5cc3a
to
b33de14
Compare
packages/kit/test/apps/basics/src/routes/redirect/crashing/__error.svelte
Show resolved
Hide resolved
One thing I realized is that people can actually handle the 404 case themselves today. You can just create a file like
|
That's indeed an alternative. But I think in my case I'd rather handle it the |
b33de14
to
26e0965
Compare
26e0965
to
4ac042a
Compare
4ac042a
to
7c39318
Compare
All tests should be passing now. I'm not sure why deploys are failing. |
Deploy failures are unrelated to your change. We need to fix. I think Netlify is caching old versions of the Netlify adapter |
Thank you so much for all the effort you put into this PR. I talked about it with the rest of the maintainers at today's maintainer's meeting and the consensus was that isn't something folks wanted to add. I put more details about that on the issue here: #1574 (comment) I'm terribly sorry as I know this must be a disappointing outcome given all the effort you've put into this PR and it would have been a lot nicer to have clarified that up front. I really appreciate everything you did to move this forward and help us get to a resolution on it though! Even though this didn't get merged it is nice that we now have an answer for folks on how they can accomplish this and we were able to knock an item off the 1.0 list thanks to the discussion this spurred |
I'd be lying if i said i'm not a little bit disappointed, but I'll get over it :) Happy to help, for sure I'll try to find another issue to knock down, maybe something more consensual :D |
that would be awesome. I went through and labeled the issues with "help wanted" where I think we're fairly agreed on a solution and it just needs to be implemented thanks again for all the help in looking at this one! |
Fixes #1574
client redirect only on browser (edgy)Tests
pnpm test
and lint the project withpnpm lint
andpnpm check
Changesets
pnpx changeset
and following the prompts. All changesets should bepatch
until SvelteKit 1.0