Switched from Sentry.captureMessage
to captureException
for better logging
no issue - `Sentry.captureMessage` is used for plain text messages rather than errors or objects
This commit is contained in:
parent
5b2194d5e8
commit
09716646b0
@ -1,5 +1,5 @@
|
||||
import Service, {inject as service} from '@ember/service';
|
||||
import {captureMessage} from '@sentry/browser';
|
||||
import {captureException} from '@sentry/browser';
|
||||
import {dasherize} from '@ember/string';
|
||||
import {A as emberA, isArray as isEmberArray} from '@ember/array';
|
||||
import {filter} from '@ember/object/computed';
|
||||
@ -102,7 +102,7 @@ export default Service.extend({
|
||||
|
||||
showAPIError(resp, options) {
|
||||
if (this.config.get('sentry_dsn')) {
|
||||
captureMessage(resp);
|
||||
captureException(resp);
|
||||
}
|
||||
|
||||
// handle "global" errors
|
||||
|
Loading…
Reference in New Issue
Block a user