Fix: newline-after-var false positive (fixes #6834)
#6847
Merged
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
|
@mysticatea, thanks for your PR! By analyzing the annotation information on this pull request, we identified @IanVS, @vitorbal and @cvisco to be potential reviewers |
|
LGTM |
|
LGTM, but waiting another day for others to look |
|
LGTM, waiting for others to review. |
|
LGTM also |
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.
Fixes #6834.
This PR fixes false positive of
newline-after-varrule for semicolon-less style.If the last token of variable declaration is semicolon and the semicolon is on a different line from the previous token of the semicolon, the rule comes to compare line between the previous token and the next statement.