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
With the current implementation, text defined in the message key is sent to Sentry with the captureMessage function. Sentry then uses this message as a title in the dashboard.
If an error object is also included, the captureException function is used instead, and Sentry uses the error's message as the title of the issue. However, the text provided as the original message isn't sent, It would be great to also include it as additional data to the issue.
I believe the following changes could resolve this problem : (line 103)
With the current implementation, text defined in the
message
key is sent to Sentry with thecaptureMessage
function. Sentry then uses this message as a title in the dashboard.If an error object is also included, the
captureException
function is used instead, and Sentry uses the error's message as the title of the issue. However, the text provided as the originalmessage
isn't sent, It would be great to also include it as additional data to the issue.I believe the following changes could resolve this problem : (line 103)
Looking at the code, I'm also wondering if including the
tags
incaptureException
is necessary since they are already configured insideconfigureScope
.The text was updated successfully, but these errors were encountered: