In regard to the no-return-await rule, the docs say the following:
Inside an async function, return await is useless. Since the return value
> of an async function is always wrapped in Promise.resolve, return await
> doesn’t
> actually do anything except add extra time before the overarching Promise
> resolves or rejects. This pattern is almost certainly due to programmer
> ignorance of the return semantics of async functions.
What about a case where I want to catch an error from the function I'm
awaiting like this:
async function foo() {
try {
return await bar();
} catch (error) {
console.log('Error caught');
}
}
Is this not a valid use of `return await`?
--
You received this message because you are subscribed to the Google Groups
"ESLint" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
