Add .editorconfig file #1336
Merged
Add .editorconfig file #1336
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
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.
While #1329 I noticed some differences in indentation styles, for instance between
.babelrcand.eslintrc. One uses spaces, the other tabs.An
.editorconfigfile helps configuring IDEs to use the right indentation style depending on file type. This way, there's no need to do this manually to follow the coding standards.The proposed
.editorconfigfile matches the WordPress core coding standards and adds exceptions for hidden files like.babelrcand.eslintrc, as well as Markdown files (trailing whitespace for simple line breaks).Fixes #51.