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
Docs: Updated no return await documentation (fixes #9695) #10699
Conversation
Get latest from ESLint
I'm not sure why the commit message (PR Title) is failing... if someone will tell me what I'm doing wrong I'll update it. Thanks! |
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.
Thanks for the PR! This looks good to me, just leaving open for a little bit in case anyone else wants to review.
I updated the PR title for you -- I think the issue was that it had a leading space.
Ah! Not sure how that happened, but thanks! I'll be watching this issue in case anyone has any other suggestions. |
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.
LGTM, thanks!
What is the purpose of this pull request? (put an "X" next to item)
[ X ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[ ] Other, please explain:
What changes did you make? (Give an overview)
Updated documentation for 'no-return-await' rule page. Reworded to make it clear that return await is usually unnecessary but there is 1 exception (trying to catch errors from a Promise-based function). Hopefully this will make folks coming to this rule page happy and we can close this issue.
Is there anything you'd like reviewers to focus on?
Yes, please make sure the wording is to your liking. Also I said from a "promise-based" function - I think this is correct (the function could be a promise or it could be an async function) but I'm not 100% sure, lmk if that is incorrect. Thanks!