Fix: no-var autofix syntax error in single-line statements (fixes #7961) #7962
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
not-an-aardvark
added
accepted
|
@not-an-aardvark, thanks for your PR! By analyzing the history of the files in this pull request, we identified @mysticatea, @alangpierce and @vitorbal to be potential reviewers. |
|
LGTM |
gyandeeps
approved these changes
Jan 21, 2017
nzakas
approved these changes
Jan 21, 2017
btmills
approved these changes
Jan 22, 2017
This was referenced Jan 25, 2017
eslint-deprecated
bot
added
the
archived due to age
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the purpose of this pull request? (put an "X" next to item)
[x] Bug fix (#7961)
What changes did you make? (Give an overview)
This updates the
no-varautofixer to avoid fixing variable declarations in single-line if/while/etc. statements, becauseletdeclarations are not allowed there.Is there anything you'd like reviewers to focus on?
This is not a particularly urgent fix -- the bug has existed since
no-varbecame autofixable in July. If we do a patch release this week then we might as well include this fix, but I don't think this bug warrants a patch release on its own.