Fix: avoid breaking eslint-plugin-eslint-comments (fixes #9193) #9196
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
|
LGTM |
ilyavolodin
approved these changes
Sep 1, 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 (#9193)
What changes did you make? (Give an overview)
This provides a fix for #9193 so that libraries like
eslint-plugin-eslint-commentswill still work.Rather than reverting d672aef and 1be5634, this tries to provide the minimum possible legacy behavior to make
eslint-plugin-eslint-commentsandeslint-plugin-githubwork, without giving rules full access to thelinterinstance again.Is there anything you'd like reviewers to focus on?
Nothing in particular