Merge ~ilasc/launchpad:eslint-fix-no-new into launchpad:master
Proposed by
Ioana Lasc
Status: | Merged |
---|---|
Approved by: | Ioana Lasc |
Approved revision: | 29b14750f2be5f50402118189382d9aa73e609a8 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~ilasc/launchpad:eslint-fix-no-new |
Merge into: | launchpad:master |
Diff against target: |
12 lines (+1/-0) 1 file modified
lib/lp/registry/javascript/tests/test_team_mailinglists.js (+1/-0) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Colin Watson (community) | Approve | ||
Review via email: mp+407006@code.launchpad.net |
Commit message
Fix no-new in test_team_
Description of the change
We need the new operator in there otherwise we fail with:
Failure in '
'/home/
'Mailinglists.
"(evaluating 'this._
To post a comment you must log in.
Generally LGTM, but could you use `eslint- disable- next-line` rather than `eslint-disable`? As I understand it, `eslint-disable` disables the rule for the rest of the block or until a matching `eslint-enable` is reached, and we don't need to be that extensive here.