Skip to content

docs: clarify which errors Astro error pages catch - #14538

Closed
sharadvc wants to merge 1 commit into
withastro:mainfrom
sharadvc:cursor/clarify-catchable-errors-e741
Closed

sharadvc wants to merge 1 commit into
withastro:mainfrom
sharadvc:cursor/clarify-catchable-errors-e741

Conversation

@sharadvc

Copy link
Copy Markdown

Summary

The error prop on 500.astro is not “any error thrown during rendering.” Per maintainer guidance, it covers failures before the response body streams (route component script / middleware at await next()), not errors thrown while HTML is streamed from templates and components.

Update that wording and link to middleware.

Fixes #12172

@astrobot-houston

Copy link
Copy Markdown
Contributor

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File Note
en/basics/astro-pages.mdx Source changed, localizations will be marked as outdated.
Warnings reference
Icon Description
🔄️ The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

@ArmandPhilippot

Copy link
Copy Markdown
Member

See #14541 (comment)

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Clarify what errors are catchable

3 participants