Question: Why use .catch on the promise about until HOT 4 CLOSED

@kettanaito Thank you!

from until.

@kettanaito I think this might be incorrect - await should throw on promise rejection

In your example you're just missing an await - add it and console.log is called:

try { await new Promise(() => { throw new Error('Hey') }) } catch (e) { console.log(e) }

from until.

@terenced can you tell me why?thank you

from until.

The .catch() block was added to propagate unhandled exceptions to the library.

When there's an exception thrown during a Promise, it will not be caught by a try/catch block around it:

try { new Promise(() => { throw new Error('Hey') }) } catch (e) { console.log(e) }

The console.log will never be called. The thrown exception will be printed as an UnhandledPromiseRejectionWarning.

Flow-wise, that is still an unsuccessful promise execution, so this library should execute the return [error, null] closure for the dependent code to handle it like an error. Adding an explicit .catch() statement to the given promise catches any errors occurring in that promise.

This solution also doesn't interfere with you defining your custom .catch(), as catch doesn't have an accumulative nature. If you've defined your custom .catch() block, it will get executed first, and the library's .catch() will not, unless you throw another exception in your own catch block.

new Promise(() => { throw new Error('Hey') }).catch(e => console.log('Custom', e)).catch(e => console.log('Library', e))

from until.