Closed
Bug 1905959
Opened 1 year ago
Closed 1 year ago
Move jsm specific rule definitions out of eslint-plugin-mozilla
Categories
(Developer Infrastructure :: Lint and Formatting, task)
Developer Infrastructure
Lint and Formatting
Tracking
(firefox129 fixed)
RESOLVED
FIXED
129 Branch
Tracking | Status | |
---|---|---|
firefox129 | --- | fixed |
People
(Reporter: standard8, Assigned: standard8)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
Due to the way the new ESLint flat configuration works with plugins, it will be easier to migrate eslint-plugin-mozilla if we have less variants of the configuration due to the different types of files.
Therefore I'd like to move the jsm specific rule handling out of eslint-plugin-mozilla (epm). I think now is a reasonable time to do it - the only support we still require in-tree is for the testing based jsms, so out of tree users of epm should have migrated already, or be prompted to.
Assignee | ||
Comment 1•1 year ago
|
||
This helps to simplify the combinations in eslint-plugin-mozilla ahead of supporting the ESLint flat config.
Pushed by mbanner@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/1c3634c8dbbb
Move jsm rule handling out of eslint-plugin-mozilla to the top-level config. r=frontend-codestyle-reviewers,Gijs
Status: NEW → RESOLVED
Closed: 1 year ago
status-firefox129:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 129 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•