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

Investigate Ember grouping #88

Closed
snmaynard opened this issue Oct 24, 2014 · 3 comments
Closed

Investigate Ember grouping #88

snmaynard opened this issue Oct 24, 2014 · 3 comments

Comments

@snmaynard
Copy link
Contributor

Ember seems to wrap errors changing the stack trace which can cause grouping issues - lets try and find a nice solution to this.

@kimroen
Copy link

kimroen commented Oct 24, 2014

I thought maybe this would be useful:

The recommended way of reporting errors from Ember is by implementing Ember.onerror, as explained here: http://emberjs.com/guides/understanding-ember/debugging/#toc_implement-an-ember-onerror-hook-to-log-all-errors-in-production

So this is pretty much how it's done with Bugsnag:

Ember.onerror = function(error) {
  Bugsnag.notifyException(error);
};

@kattrali
Copy link
Contributor

@kattrali
Copy link
Contributor

v0.2.0 of Ember Bugsnag was just released.

kattrali pushed a commit that referenced this issue Apr 26, 2021
…lugin-in-tests

Enable client state persistence plugin in tests
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

3 participants