I Don't use Promises on a daily basis. But when I do, all I need is a simple usage example of how to handle them. What I find instead are over comp...
For further actions, you may consider blocking this person and/or reporting abuse
What's the reason to have promise hell in the first example when you can just chain promises one after another?
Not sure what you mean.
You just removed the
.catch(), which means you do not handle in case of rejection.You can chain the Promises. Inside of .then(), you can return another promise and it'll let you add another .then() underneath. You add a single .catch() at very end, which will work for all the .then() chains.
Yeah, as Joel mentioned, you can return promises to get one flat promise chain.
Imagine that you have 4 promises. If you follow example 1 in your post, you'll get promise structure like callback hell, but if you return next promise in every
then, you'll get nice and flat promise chain.Oh, now I understand.
Wow, this is worth editing the original post!
Thanks!
Another improvement you can make is not using anonymous function
It gives you testability and readability
So instead of:
longPromise()
.then((data)=>{
console.log(data); // logs: longPromise resolved
return shortPromise();
.then((data)=>{
console.log(data) // logs: shortPromise resolved
})
.catch((error)=> {
console.log(error);
})
});
you can do:
async function firstHandler(data){
console.log(data)
return shortPromise()
}
longPromise.then(firstHandler).then(console.log).catch(console.log)
Hey Ori,
Looks good,
I'd add a few 'Gotchas' and maybe some more information here!
When using async/await it's very difficult to use finally and catch, async await only deals with 'resolve'
Promises are a great way (and I think the only way) to add a micro task into the event loop, micro tasks are the only way to ensure execution before the next tick. (done with Promise.resolve())
You could probably await a Promise.all() as well, as it returns a promise
Other than that, good stuff!
Thanks!