Replies: 1 comment
-
Here is the block of code for reference: remix/packages/remix-server-runtime/server.ts Lines 512 to 550 in 1fd7096 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What is the new or updated feature that you are suggesting?
The framework should allow developers to handle unhandled errors that are thrown within loaders/actions within resource routes.
Why should this feature be included?
Errors that are thrown within these routes are captured and automatically processed by the framework. This leads to the error being logged to the console and an internal server error response being returned to the caller. This makes sense for document requests since a developer is able to use a
CatchBoundary
orErrorBoundary
to get access to the error that was thrown.The particular scenario that this affects is error logging/monitoring. Currently the automatic logic makes it difficult to globally send these errors to Sentry and/or some other external service without wrapping
try
/catch
blocks around each instance.Beta Was this translation helpful? Give feedback.
All reactions