-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Framework: Use an eslintrc with a specific format #2664
Merged
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
blowery
added
Framework
[Status] Needs Review
The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically.
labels
Jan 21, 2016
'vars-on-top': 1, | ||
'yoda': 0 | ||
} | ||
} |
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.
missing semicolon?
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.
nice catch.
🚢 |
gwwar
added
[Status] Ready to Merge
and removed
[Status] Needs Review
The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically.
labels
Feb 2, 2016
Prior we were using an .eslintrc, which is supposed to be either JSON or YAML. This is now deprecated, in favor of .eslintrc., like .eslintrc.js for JavaScript. See http://eslint.org/docs/user-guide/configuring#using-configuration-files for more details. This patch moves to an .eslintrc.js and alters the format a bit to export the configuration object as the default, as per the config guide.
who will lint the linters?
blowery
force-pushed
the
fix/eslint-config-file
branch
from
February 2, 2016 20:23
92d1d74
to
1bd1800
Compare
blowery
added a commit
that referenced
this pull request
Feb 2, 2016
Framework: Use an eslintrc with a specific format
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.
Prior we were using an .eslintrc, which is supposed to be either JSON or YAML. This is now deprecated, in favor of .eslintrc., like .eslintrc.js for JavaScript. However, our config has comments in it, which are not legal JSON, so we should really move to the JS format.
See http://eslint.org/docs/user-guide/configuring#using-configuration-files for more details.
This patch moves to an .eslintrc.js and alters the format a bit to export the configuration object as the default, as per the config guide.