Closed
Bug 1579414
Opened 5 years ago
Closed 3 years ago
[meta] Enable ESLint rule no-async-promise-executor everywhere on the tree
Categories
(Developer Infrastructure :: Lint and Formatting, task, P3)
Developer Infrastructure
Lint and Formatting
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: standard8, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: meta)
When we upgraded to ESLint 6, we disabled the no-async-promise-executor rule for various files as it wasn't a quick enable.
This bug is for tracking the bugs to get that turned on fully.
Some notes about this rule (from ESlint's site):
The Promise executor function can be an async function. However, this is usually a mistake, for a few reasons:
- If an async executor function throws an error, the error will be lost and won’t cause the newly-constructed Promise to reject. This could make it difficult to debug and handle some errors.
- If a Promise executor function is using await, this is usually a sign that it is not actually necessary to use the new Promise constructor, or the scope of the new Promise constructor can be reduced.
Reporter | ||
Comment 1•3 years ago
|
||
Looks like we fixed this in the bugs this depends on.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Firefox Build System → Developer Infrastructure
You need to log in
before you can comment on or make changes to this bug.
Description
•