Discussion on "The Most Important Thing You Don't Know About Promises"

Yogesh Chavan · 2021-06-22T08:29:45.584Z

Take a look at the below code: const promise = new Promise((resolve, reject) => { resolve(); }); promise .then(() => { console.log('first'); }) .then(() => { console.log('second'); }) .then(() => { console.log('third'); }) ...

Great article. I have stuck in this problem before. I wonder if there's a way to solve this by using async-await instead of promises.

Himanshu Kumar If you're using async/await, you don't need to worry about this problem because when using await keyword, the next line will not be executed until the promise we're awaiting for gets resolved/rejected.

Yogesh Chavan That makes sense. Thanks for clarifying.

Awesome content. Thanks Yogesh! I was wondering as for API call we mostly use axios which also returns a Promise by default, we will not have to explicitly return a promise from inside a then block. Obviously for other use cases where things don't return promise we have to do the one you did. Please correct me if I am wrong.

Thanks SOIF RIWAJ.

Yes, for axios we don't need to deal with this issue most of the time. But If you're doing some asynchronous operation in the .then handler then you need to be aware of this issue.

Wow-some article as usual Yogesh Chavan, this is a refreshment for me 🤗, thanks a lot for sharing 😊

Glad to hear that. Thanks for reading Ayodele Samuel Adebayo

Discussion

The Most Important Thing You Don't Know About Promises

Responses(3)

Recent in Forum

Search Hashnode

The Most Important Thing You Don't Know About Promises

Responses(3)

Recent in Forum