Consider exposing promise unhandled rejection hook

[benjamingr]

Hey, I've written the following proposal here: https://gist.github.com/benjamingr/0237932cee84712951a2

I'd love your feedback.

[stefanpenner]

it is exposed. RSVP.on('error'

[benjamingr]

@stefanpenner right, and I'm asking you expose it on "process" in addition like the proposal says, Please consider reading it :p

[stefanpenner]

Sounds good. I'll add it to rsvp and es6promise this weekend

[benjamingr]

Awesome - thanks a ton :)

[stefanpenner]

thanks for investing in the promise community :)

[vkurchatkin]

please, don't emit this event on process object. It could end up conflicting with native node.js/io.js implementation or other libs. If the purpose is to share emitter between dupes, the event should be namespaced somehow (e.g. process.on('rsvp:possiblyUnhandledRejection'))

[stefanpenner]

@benjamingr thoughts?

[benjamingr]

@stefanpenner

The whole idea here is to is to fire the same events as native promises and with other libraries so you get a global place to handle every promise error from any library (or native promises) in one place - please see the design document (at the start of the issue) on what problems it solves.

What @vkurchatkin is describing is why we want to do this.

[vkurchatkin]

@benjamingr the idea is good, but there is a reason why developing a standard takes time. There is no consensus on how this should be done.

[benjamingr]

@vkurchatkin I believe there is, and several libraries have already implemented this. This standard is just a minimal first stage as a preparation for more interesting standards and ideas which is why all it takes is exposing two events on process and nothing more.

If you have any interesting feedback I would greatly value it here: https://gist.github.com/benjamingr/0237932cee84712951a2

You can also find me regularly in the Stack Overflow JavaScript chatroom and I tend to frequent #promises too. You can also contact me by email if you'd prefer (benji at tipranks) (dot com)