-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Coerces error-like objects (with stack properties) into strings #866
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
Comments
Hi @benvinegar, any update regarding this? Or any chance to give a hint and/or point out where the change should be made? Regards! |
Maybe passing something like: || !!what.stack Somwhere around here (src/utils.js#L14) or here (plugins/ember.js#L22) (disclaimer: educated guess) |
There's no point in making this check looser if Sentry is just going to blow up on the object anyways. (e.g. if it's an array of errors). I still don't have a reproduction case (per the other thread in ember-cli-sentry). |
We already improved those checks quite a bit. |
Raven.js checks if objects passed to
Raven.captureException
are errors using ourisError
helper, which is pretty strict: it basically checks if the object in question "descends" fromError
using aninstanceof
check.But there are some error-like objects out there (e.g. Ember.js) that have
.stack
properties but do not pass theinstanceof Error
check. We should probably handle these too.See: ember-cli-sentry/ember-cli-sentry#72
The text was updated successfully, but these errors were encountered: