-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Nested error components #519
Comments
Crazy thought -- should error pages belong in layout pages? |
This was referenced Apr 3, 2021
Closed
Merged
Rich-Harris
pushed a commit
that referenced
this issue
Apr 5, 2021
Rich-Harris
pushed a commit
that referenced
this issue
Apr 5, 2021
This was implemented back in #901. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have nested
$layout
components, but only a top-level$error
. It might be useful to support nested error components as well:In this example, if
routes/settings/notifications/$error.svelte
errored in load, we'd then try renderingroutes/settings/$error.svelte
, etc.The text was updated successfully, but these errors were encountered: