Closed
Bug 1579452
Opened 5 years ago
Closed 5 years ago
Enable ESLint rule no-async-promise-executor on disabled locations for devtools
Categories
(DevTools :: General, task, P3)
DevTools
General
Tracking
(firefox71 fixed)
Tracking | Status | |
---|---|---|
firefox71 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
References
Details
Attachments
(1 file)
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 devtools/
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.
Assignee | ||
Comment 1•5 years ago
|
||
Depends on D45010
Assignee | ||
Comment 2•5 years ago
|
||
Try push: https://treeherder.mozilla.org/#/jobs?repo=try&revision=1009ca9870c5663c1103e622f17066d54b829e8e
Assignee: nobody → standard8
Status: NEW → ASSIGNED
Iteration: --- → 71.2 - Sept 16 - 29
Points: --- → 1
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/44d3b8582d36
Enable ESLint rule no-async-promise-executor on disabled locations for devtools. r=jlast
Comment 4•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox71:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 71
You need to log in
before you can comment on or make changes to this bug.
Description
•