chore: add no-async-promise-executor as it becames recommanded #15261
+50
−52
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
23 tasks
Lemonexe
reviewed
Nov 6, 2024
peter-sanderson
force-pushed
the
no-async-promise-executor
branch
2 times, most recently
from
38808e2
to
d4fb4c5
Compare
Lemonexe
reviewed
Nov 7, 2024
peter-sanderson
force-pushed
the
no-async-promise-executor
branch
from
d4fb4c5
to
aa412df
Compare
Lemonexe
approved these changes
Nov 7, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://eslint.org/docs/latest/rules/no-async-promise-executor
I just ignored 2 occurrences we have so far. This way we can fix them later and we are warn to not create another.