Skip to content

Conversation

@YashSharma64
Copy link

This update refines the existing ErrorBoundary by improving its stability and clarity without altering its core behavior. The cleanup removes development-only console logs and ensures the captured error context is consistent for Sentry. Overall, the component becomes quieter, cleaner, and more aligned with production best practices while continuing to fall back gracefully to the 404 view.

This update refines the existing ErrorBoundary by improving its stability and clarity without altering its core behavior.
The cleanup removes development-only console logs and ensures the captured error context is consistent for Sentry.
Overall, the component becomes quieter, cleaner, and more aligned with production best practices while continuing to fall back gracefully to the 404 view.
@YashSharma64
Copy link
Author

Hey! Hope you're doing well.
This PR includes a small improvement to make the ErrorBoundary’s Sentry reporting cleaner and more consistent. No behaviour changes, just a bit of polish to help with clearer debugging.
Whenever you get a moment, I’d appreciate your review.
Happy to adjust anything if needed. Thanks!

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.

1 participant