This repository has been archived by the owner on Mar 25, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 888
no-unused-new: should not be triggered #1839
Closed
Comments
The implementation of |
4 tasks
nchen63
pushed a commit
that referenced
this issue
Mar 10, 2017
Integrate `no-unused-new` into this rule. [new-rule-option] `allow-new-side-effects` restores the old behaviour to allow `new` for side effects [bugfix] allow comma separated assignments Fixes: #2058 [bugfix] allow indirect eval: `(0, eval)("");` [enhancement] checking for unused new can now use option `allow-fast-null-checks` Fixes: #1839 [enhancement] find unused comma separated expressions in all locations of the code [enhancement] find unused expressions inside void expression
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug Report
4.0.2
2.1.4
TypeScript code being linted
with
tslint.json
configuration:Actual behavior
[tslint] do not use 'new' for side effects (no-unused-new)
Expected behavior
No lint error
The text was updated successfully, but these errors were encountered: