-
Notifications
You must be signed in to change notification settings - Fork 6.8k
refactor: clean out variables that are being assigned to but not being read #9871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should we add a lint check to stop them from creeping back in?
tslint will start catching them when we update to TS 2.6 @mmalerba. I didn't bump to TS 2.6 in this PR, because there are some build issues that we'll need to sort out. |
b5e46c3
to
4a9f2e5
Compare
@crisbeto please rebase |
Updating to |
ce66095
to
649219f
Compare
Rebased @josephperrott. |
…g read Clears out private properties and local variables that are declared and assigned values, but aren't actually being read at any point. This will start being caught by tslint once we update to TS 2.6.
649219f
to
eb760b6
Compare
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Clears out private properties and local variables that are declared and assigned values, but aren't actually being read at any point. This will start being caught by tslint once we update to TS 2.6.