As a mozilla-central developer, any changes I make to browser/components/newtab should be linted like other parts of m-c, so that key style & defect types are caught/fixed more efficiently.
After eslint gets vendored into mozilla-central, we'll want to land our own specific eslint plugins there as well, so that we can then remove activity-stream from the top-level .eslintignore and have it get first-class linting support in-tree. There was some discussion about wanting in-tree unit-testing as a prerequisite, so that broad changes are less-likely to introduce issues that should have been caught.
Status: NEW → RESOLVED
Closed: 9 days ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1553917
You need to log in before you can comment on or make changes to this bug.