4 ms·
To give Ember some criticism, we're struggling with debugging at the moment: The main issue https://github.com/emberjs/ember.js/issues/2817 https://github.com/
by mjallday 13y ago
To give Ember some criticism, we're struggling with debugging at the moment:
The main issue https://github.com/emberjs/ember.js/issues/2817 https://github.com/emberjs/ember.js/issues/2817 is that the run loop in Ember disassociates the invoking action from the event handler which makes figuring out what fired what a PITA.
That and the stacktraces are useless makes hunting down bugs often more difficult than it should be.
I don't know how this contrasts with other JS frameworks but we definitely feel the pain with this issue.
- ulisesrmzroche 13y agoOh god yeah. It really sucks. This is going to be a pain with anything async right now though.
- mjallday 13y agoI assume there's a way to add context information into the run loop when firing events for debugging purposes. This would largely solve the first half of the issue (who fired the event). The second half, where the error happened, seems like it's just a bug in the way Ember is recording errors.
- ulisesrmzroche 13y agoThis I'm not too sure about. I know they're moving this to https://github.com/ebryn/backburner.js https://github.com/ebryn/backburner.js. I'll read through the code sometime tonight and figure out what's going on.
- MetaCosm 13y agoI really wish more articles about frameworks were about the ugly bits. If you do exactly what the framework expects and never go off the reservation, they all are fairly decent. What I want to always know about is what happens in the framework when stuff goes bad. "When frameworks go bad, your guide to life after the honeymoon period"... I would read that.