Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

console.warn() should send level:'warning', not 'warn' #342

Closed
chromakode opened this issue Apr 17, 2015 · 2 comments
Closed

console.warn() should send level:'warning', not 'warn' #342

chromakode opened this issue Apr 17, 2015 · 2 comments

Comments

@chromakode
Copy link

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?

@mattrobenolt
Copy link
Contributor

lol, yeah, definitely a bug.

@chromakode
Copy link
Author

Thanks! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants