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
It appears that console.warn() messages are being classified as errors in my Sentry listing.
When I send a message via Raven.captureMessage('hello', {level:'warn'}), the level shows up in the Sentry details as level = error (perhaps the Sentry backend is doing this reclassification?). However, Raven.captureMessage('hello', {level:'warning'}) is displayed as a warning in Sentry as intended.
I think that the console plugin should be tweaked to send a 'warning' level instead of 'warn'. Does this make sense?
The text was updated successfully, but these errors were encountered:
It appears that
console.warn()
messages are being classified as errors in my Sentry listing.When I send a message via
Raven.captureMessage('hello', {level:'warn'})
, the level shows up in the Sentry details aslevel = error
(perhaps the Sentry backend is doing this reclassification?). However,Raven.captureMessage('hello', {level:'warning'})
is displayed as a warning in Sentry as intended.I think that the console plugin should be tweaked to send a
'warning'
level instead of'warn'
. Does this make sense?The text was updated successfully, but these errors were encountered: