Add mechanism to captureException calls #17237
Closed
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.
Before submitting a pull request, please take a look at our
Contributing guidelines and verify:
yarn lint) & (yarn test).This PR standardizes
captureExceptioncalls across all Sentry JavaScript SDK packages by ensuring every call includes amechanismobject withhandledandtypeproperties.This change provides richer context for captured exceptions, improving their actionability in Sentry:
handled: Set based on whether the SDK code path explicitly handles the error (e.g., via user-provided fallbacks) or if it's an unexpected, unhandled error.type: Specifies the SDK package and, where possible, a more granular context (e.g.,nextjs.route,nestjs.graphql,supabase,openai).Learn more about Cursor Agents