Closed Bug 1425047 Opened 4 years ago Closed 2 years ago

Enable ESLint rule no-undef for mobile/android/chrome


(Firefox for Android Graveyard :: General, enhancement, P5)



(firefox74 fixed)

Firefox 74
Tracking Status
firefox74 --- fixed


(Reporter: standard8, Assigned: standard8)




(4 files)

Currently the mobile/android/chrome directory reports a lot of no-undef issues.

I think a lot of these are the fact that ESLint doesn't know the actual globals that are available.

It might be that we need something equivalent to the browser-window environment (that we use for browser/base/content), that works out the mobile globlals.
Priority: -- → P3
Re-triaging per

Needinfo :susheel if you think this bug should be re-triaged.
Priority: P3 → P5

With the various removals that have gone on and mainly just geckoview left, there's no much to do here to enable the no-undef and no-unused-vars rules.

Additionally, getting the other rules passing that we didn't have passing before is also easy to do.

Hence, I've just done a few patches to get this tidied up. The only bit of remaining enabling would be bug 1424996, but that didn't seem worth it as bug 1583370 will likely make that bit go away.

Assignee: nobody → standard8
Iteration: --- → 74.2 - Jan 20 - Feb 09
Points: --- → 2

This enables consistent-return, no-empty and no-redeclare.

Depends on D60826

Pushed by
Enable ESLint rules no-undef and no-unused-vars for mobile/android/chrome/geckoview. r=esawin
Enable already passing rules for mobile/android. r=esawin
Enable ESLint rule object-shorthand for mobile/android. r=esawin
Enable rest of ESLint rules for mobile/android. r=esawin
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.