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
Wire up console.warn/console.error to Raven.captureMessage #85
I wouldn't object to you adding it but I do wonder whether it would just encourage people to send poorly crafted log messages rather than integrate logging correctly.
usually when you do a Raven.captureMessage or captureException, you could put a console.log there if you like, or write a small wrapper for yourself, would be like two lines of code for the developer.
Edit: Really the developer should be wrapping calls to Raven.capture* anyways, otherwise you're really coupling yourself to the Raven implementation.
Activity
defunctzombie commentedon Mar 14, 2013
No.
acdha commentedon Mar 14, 2013
I'm -0 on this - seems like it'd be noisy and only helps developers who'd be in a position to do it the right way instead.
mattrobenolt commentedon Mar 14, 2013
@acdha , it would be behind a log level setting. So you'd say,
Raven.config(..., {level: 'warn'})so you can control how much noise you want.acdha commentedon Mar 14, 2013
I wouldn't object to you adding it but I do wonder whether it would just encourage people to send poorly crafted log messages rather than integrate logging correctly.
bisrael commentedon Mar 15, 2013
usually when you do a Raven.captureMessage or captureException, you could put a console.log there if you like, or write a small wrapper for yourself, would be like two lines of code for the developer.
Edit: Really the developer should be wrapping calls to Raven.capture* anyways, otherwise you're really coupling yourself to the Raven implementation.
mattrobenolt commentedon Oct 21, 2013
This is done with the console plugin.
chore(replay): Upgrade `rrweb` to 1.108.0