-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
chore: let @typescript-eslint/no-floating-promises
ESLint rule pass
#6331
Conversation
|
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.
I don't think this needs a changeset since it's internal cosmetics
@typescript-eslint/no-floating-promises
ESLint rule pass
887fa54
to
accc510
Compare
Thank you for signing the Contributor License Agreement. Let's get this merged! 🥳 |
accc510
to
7f6e2f6
Compare
@pcattori This made code changes that #6248 didn't make, specifically the fix to withApp.ts#L39 is a test runtime behavior improvement. There were no eslint rule changes in this pull request. I think this pull request should be re-opened. |
@MichaelDeBoey just checking in, is there anything else left on this PR? I'm working on the other recommended typed rules from typescript-eslint and saw this one is still hanging around. |
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, just needs conflicts with dev
to be resolved
7f6e2f6
to
2a34e48
Compare
I've rebased the branch, re-ran the no-floating-promises rule, and updated where there were new errors. |
Sorry it looks like this has new conflicts 😬 . I merged dev in locally but don't have access right to push to your fork |
error Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator @typescript-eslint/no-floating-promises
error Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the `void` operator @typescript-eslint/no-floating-promises
2a34e48
to
c4a362c
Compare
@brophdawg11 I re-resolved the conflicts and made sure formatting was applied to Because I forked into a separate org, to organize my GitHub forks, I don't have the option to enable maintainers to push to the branch. I didn't realize that was a drawback at the time. |
🤖 Hello there, We just published version Thanks! |
Summary of changes
This is just the relevant parts of the code changes from #6325 instead of also tackling eslint-config changes.
void
operator to Promises that are not being awaited. Usedawait
on finally retry in test.Details
When enabling the typescript-eslint rules contained in "plugin:@typescript-eslint/recommended-requiring-type-checking" I tried to improve code quality by addressing some of the issues raised when enabling the type checked linting rules.
This change specifically resolves issues raised with the typescript-eslint error:
no-floating-promises
.Testing Strategy:
The specific rule configuration was: