Discussion: Conversion of NSException to NSError about promises HOT 6 CLOSED

I believe handling ObjC exceptions is indeed an error prone overkill, so let's get rid of that behavior.
Many thanks for raising the issue, Tom!

from promises.

Hi @shoumikhin,
Looks like you haven't updated the docs regarding this behaviour.

from promises.

@shali3 The docs don't explicitly mention exceptions at all and in my opinion this is fine. The library doesn't catch exceptions anymore which is the default and expected behavior for any library in Objective C so it's not necessary to state that exceptions are not catched.

from promises.

From the docs (link in my previous comment):

Observing rejection
To get notified when a promise is resolved with an error (i.e. is rejected), use the catch operator.

You can reject a promise in many ways:

call reject method on a promise
call reject() in an async block or return an error from the do block
return or throw an error from the then block
Or, just create a resolved promise with an error.

from promises.

It's talking about throwing an error, not an exception which most probably refers to Swift Errors but you're right it's confusing at least. Maybe the word "Swift" should be added.

from promises.

From an ObjC perspective when I read error I think of NSError.

from promises.