Add base ESLint and EditorConfig configurations #166
Merged
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
nylen
pushed a commit
that referenced
this pull request
Mar 16, 2017
Add base ESLint and EditorConfig configurations
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.
This pull request seeks to add base ESLint and EditorConfig configurations. This should help myself and other developers discover erroneous or stylistically incorrect code. It uses the
eslint-config-wordpressbase configuration, extended with additional rules. Sincetinymce-per-blockdefines its own ESLint configuration asroot, there should be no conflict with this configuration (cc @youknowriad).