You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of #6586 we have a standard way of dealing with errors in a SvelteKit app. It would make sense if we respected the App.PageError shape in src/error.html.
Describe the proposed solution
Change %sveltekit.message% to %sveltekit.error.message%. We could include other properties on the error object, but there are some caveats here (we can't allow any way for src/error.html to blow up during rendering) so for now we should probably just make that change, and worry about surfacing %sveltekit.error.code% or whatever as a post-1.0 thing
Alternatives considered
No response
Importance
would make my life easier
Additional Information
No response
The text was updated successfully, but these errors were encountered:
dummdidumm
changed the title
replace %sveltekit.error% with %sveltekit.error.message%
replace %sveltekit.message% with %sveltekit.error.message%Sep 7, 2022
Describe the problem
As of #6586 we have a standard way of dealing with errors in a SvelteKit app. It would make sense if we respected the
App.PageError
shape insrc/error.html
.Describe the proposed solution
Change
%sveltekit.message%
to%sveltekit.error.message%
. We could include other properties on theerror
object, but there are some caveats here (we can't allow any way forsrc/error.html
to blow up during rendering) so for now we should probably just make that change, and worry about surfacing%sveltekit.error.code%
or whatever as a post-1.0 thingAlternatives considered
No response
Importance
would make my life easier
Additional Information
No response
The text was updated successfully, but these errors were encountered: