Closed
Bug 1800319
Opened 3 years ago
Closed 3 years ago
Promote ESLint rule no-console to an error in newtab code (but allow console.error calls)
Categories
(Firefox :: New Tab Page, task)
Firefox
New Tab Page
Tracking
()
RESOLVED
FIXED
108 Branch
Tracking | Status | |
---|---|---|
firefox108 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
Details
Attachments
(1 file)
I'm working towards replacing Cu.reportError
with console.error
.
The newtab code currently has an ESLint warning to disallow use of console
. The problem with newtab's usage is that where console.error
has been used, the rule get explicitly disabled in many places, and where something else has been used, it either gets turned off, or the warning is ignored.
If we still require the rule, then I think we should change it to be an error (so that issues actually get fixed), but allow console.error
as an acceptable use.
Assignee | ||
Comment 1•3 years ago
|
||
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ed64ba0e117d
Change newtab code so that the ESLint rule no-console is an error, except for console.error calls. r=Mardak
Comment 3•3 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox108:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 108 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•