Figure out the combination of valid-lazy rule and using declareLazy/defineLazy
Categories
(Developer Infrastructure :: Lint and Formatting, task)
Tracking
(firefox142 fixed)
| Tracking | Status | |
|---|---|---|
| firefox142 | --- | fixed |
People
(Reporter: zombie, Assigned: mbeier)
References
(Blocks 1 open bug)
Details
Attachments
(2 files, 1 obsolete file)
We probably want to make the valid-lazy rule work with the new design of declareLazy() (from bug 1945464), or at least defineLazy(this, ...) usage, because TS doesn't actually understand it and we'll need to fall back to eslint for checking it.
| Reporter | ||
Updated•1 year ago
|
Comment 1•1 year ago
|
||
Bug 1960233 (https://phabricator.services.mozilla.com/D245364 ) added 31 new uses of /* eslint-disable mozilla/valid-lazy */ to basically the whole extension framework.
In response to my question "What is the path towards restoring valid-lazy?", Tom replied with:
Mark mentioned he's going to do a similar patch to this one in toolkit/components/search later this week, so I expect he'll probably have a better idea what we might do after that.
So, just to make sure that this doesn't fall through the cracks - Mark, is there a path towards restoring valid-lazy coverage for extension code?
Comment 2•1 year ago
|
||
The existing valid-lazy rule needs either to support the new functions, or a second rule written which supports those (and adapt the current one to ignore).
At the moment I probably won't get to those for a week or two as I have other priorities. I'm happy if anyone else wants to take a look though.
| Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
| Assignee | ||
Comment 4•1 year ago
|
||
| Assignee | ||
Comment 5•1 year ago
|
||
| Assignee | ||
Updated•1 year ago
|
Comment 8•1 year ago
|
||
| bugherder | ||
Description
•