Closed Bug 1986283 Opened 2 months ago Closed 2 months ago

Add a tier-3 TypeScript linter for Firefox code

Categories

(Developer Infrastructure :: Lint and Formatting, task, P3)

Tracking

(firefox144 fixed)

RESOLVED FIXED
144 Branch
Tracking Status
firefox144 --- fixed

People

(Reporter: standard8, Assigned: standard8)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Adding an intermediate step for bug 1975512. I would like to add a tier-3 linter, so that code review starts picking up TypeScript errors and reporting them - we've had a few "regressions" on the address bar and search code, so I would like to start catching those.

As there's still a few things that I think should continue blocking the tier-2 set-up, adding a tier-3 gets us going in the right direction, and I think I've figured out the parts to make that work.

It is probably not ideal, since other areas of the code base may impact on the directories being linted, but I think getting something set up will help inform how we handle that going forward.

It also won't cover all of the errors that we currently have passing - I'm intentionally limiting the scope to being with to allow time to assess the impacts.

Pushed by mbanner@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/bc4492384926 https://hg.mozilla.org/integration/autoland/rev/da579b70f01b Add a tier-3 TypeScript linter. r=linter-reviewers,releng-reviewers,jcristau,ahal
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: