Promise.then(DoneCallback) does not fail if onDone fails about jdeferred HOT 5 CLOSED

In my case I wanted to change that behaviour so on top of #7 fix/workaround, I created another branch to have .then behave correctly on piping. Again, propably I could do some cleanup if you consider a pull-request.

from jdeferred.

thanks @mehiel ! I'll be on a roadtrip for a week or 2. i'll take a look in detail once i'm back.

from jdeferred.

@saturnism, have fun and maybe we can elaborate on these things when you'll be back!

from jdeferred.

@mehiel i'm back and i've been researching into this a bit. it seems like done callbacks shouldn't have the ability to reject - because in order to trigger done callback, a resolve was already called and state is already changed?

what do you feel if the exception is handled within the callback itself, or maybe have an unexpected exception callback?

A implementation that looks pretty clean is using then/pipe and returning a new deferred object - this is something that can't be done in current jdeferred implementation, but it seems worthwhile to pursue.

http://stackoverflow.com/questions/13798770/unable-to-reject-jquery-deferred-with-a-piped-function-if-it-was-resolved-by-a-p

from jdeferred.

see issue #10 for piping. It is closer to what jQuery does.

from jdeferred.