Promote the TypeScript linter to Tier-1
Categories
(Developer Infrastructure :: Lint and Formatting, task, P3)
Tracking
(Not tracked)
People
(Reporter: standard8, Unassigned)
References
(Depends on 3 open bugs, Blocks 1 open bug)
Details
Once the dependant bugs have been fixed, we should be ready to promote the linter added in bug 1975512 to tier-1.
|
Reporter | |
Comment 1•8 months ago
|
||
Something to potentially consider here is how the linter is run across the tree - it is possible that changes to JavaScript files or even idl files could have an impact on types, and therefore affect the TypeScript results. Hence, when we get to this stage (or maybe before), the linter should probably be running across the whole tree for any relevant change. The fact that TypeScript also can't run for just a single file potentially affects this as well.
See also :ahal's comments here.
This might affect how we want to be able to run/integrate the linter. We may need to separate it out from ./mach lint into its own command and handle it slightly differently on the code review.
For now, we're landing a tier-3 linter in bug 1986283, that will help us understand how using the existing infrastructure affects things.
Description
•