New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(eslint-plugin): no-floating-promises - support chain expression #3826
fix(eslint-plugin): no-floating-promises - support chain expression #3826
Conversation
Thanks for the PR, @mwhitworth! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day. |
await returnsPromise?.(); | ||
returnsPromise()?.then( | ||
() => {}, | ||
() => {}, | ||
); | ||
returnsPromise() | ||
?.then(() => {}) | ||
?.catch(() => {}); | ||
returnsPromise()?.catch(() => {}); | ||
returnsPromise()?.finally(() => {}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
aren't all of these valid still?
They all either are await
ed, or have a catch
/finally
to close off the promise.
Fixed in #4096 instead |
I can't see a reason why chain expressions aren't supported -
await undefined
is a no-op, and other than that they behave like member expressions