You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Put Error.cause in error data with ExtraErrorData integration #7051
Hi, thanks for writing in! The reason the integration currently doesn't support cause is because that field is not enumerable and we're simply iterating over all of the fields when adding the extra data. We could probably add a case for cause with not too much effort. Currently, though, I am not sure when we will get to it but you could open a PR to speed up the process!
changed the title [-]ExtraErrorData doesn't support Error.cause[/-][+]Put `Error.cause` in error data with `ExtraErrorData` integration[/+]on Feb 6, 2023
Activity
lforst commentedon Feb 6, 2023
Hi, thanks for writing in! The reason the integration currently doesn't support
causeis because that field is not enumerable and we're simply iterating over all of the fields when adding the extra data. We could probably add a case forcausewith not too much effort. Currently, though, I am not sure when we will get to it but you could open a PR to speed up the process![-]ExtraErrorData doesn't support Error.cause[/-][+]Put `Error.cause` in error data with `ExtraErrorData` integration[/+]lbogdan commentedon Feb 6, 2023
In the meanwhile I replaced it with a
beforeSendhandler where I use something likewhich returns
Another related small nit is that when the error has no extra data, an empty object
{}is still added tocontexts, showing an empty section in the UI:s1gr1d commentedon Jan 15, 2025
Closed because it was added here: #9914