Repository navigation
Include error.message in ErrorBoundary for better Sentry grouping - #347
Merged
Merged
Conversation
…ping Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
MykhailoAlekseiev21
force-pushed
the
error-boundary-include-message
branch
from
March 11, 2026 14:51
ff6953c to
abf152d
Compare
bodia-uz
approved these changes
Mar 11, 2026
itsh01
approved these changes
Mar 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
error.messagealongsideerror.nameinErrorBoundary.componentDidCatchlog outputErrorBoundary(shell / Comp): TypeErrortoErrorBoundary(shell / Comp): TypeError | Cannot read property 'foo' of undefinedMotivation
Currently,
ErrorBoundary.componentDidCatchlogs errors using onlyerror.name(e.g."TypeError","Error"). Since most thrown errors share a handful of generic type names, Sentry groups many unrelated failures into one mega-issue per component. This makes it difficult to triage and prioritize individual bugs.By appending
error.messageto the log string, each unique error produces a distinct fingerprint in Sentry. This splits the mega-issues into separate, actionable entries — making it much easier to identify, track, and resolve individual failures.🤖 Generated with Claude Code