Closed Bug 1431069 Opened 7 years ago Closed 7 years ago

Make eslint deal with ChromeUtils-imported globals

Categories

(Developer Infrastructure :: Lint and Formatting, enhancement)

enhancement
Not set
normal

Tracking

(firefox59 fixed)

RESOLVED FIXED
mozilla59
Tracking Status
firefox59 --- fixed

People

(Reporter: Gijs, Assigned: Gijs)

References

Details

Attachments

(1 file)

In bug 1425611 and deps we're switching from Cu.import to ChromeUtils.import . To facilitate this, we need eslint to understand that they're effectively equivalent.
See Also: → 1431104
Comment on attachment 8943240 [details] Bug 1431069 - allow eslint to deal with ChromeUtils imports, https://reviewboard.mozilla.org/r/213568/#review219680
Attachment #8943240 - Flags: review?(standard8) → review+
Hmm, so I just realised we should update our other rules as well - no-import-into-var-and-global and no-single-arg-cu-import - otherwise we run the risk of regressing with ChromeUtils. The tests for those should also be updated. I'd like that to be done before we start migrating everyone across.
Flags: needinfo?(gijskruitbosch+bugs)
(In reply to Mark Banner (:standard8) from comment #3) > Hmm, so I just realised we should update our other rules as well - > no-import-into-var-and-global and no-single-arg-cu-import - otherwise we run > the risk of regressing with ChromeUtils. The tests for those should also be > updated. > > I'd like that to be done before we start migrating everyone across. Ah, good points. Done. :-)
Flags: needinfo?(gijskruitbosch+bugs)
Pushed by gijskruitbosch@gmail.com: https://hg.mozilla.org/integration/autoland/rev/046fb034b323 allow eslint to deal with ChromeUtils imports, r=standard8
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Product: Testing → Firefox Build System
Product: Firefox Build System → Developer Infrastructure
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: