Add .eslintrc to ensure that editor plugins will use the correct config #928
Conversation
This file contains hidden or 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
ghost
merged commit
hackygolucky
added a commit
to hackygolucky/nodejs.org
that referenced
this pull request
Sep 29, 2016
* upstream/master: Add .eslintrc to ensure that editor plugins will use the correct config (nodejs#928)
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I have a globally defined
.eslintrcwhich is used by my editor plugin when a project specific.eslintrcis not found.I don't use the
standardstyle as my default so whenever I open a file in this project my editor turns into a Christmas tree with warnings and errors everywhere.This adds a local
.eslintrcwhich simply extends thestandardconfig to fix the issue.