Add a .editorconfig file #62
Open
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
Add a .editorconfig file Add a .editorconfig file
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.
Add a .editorconfig file
Install ECLint by typing:
$ npm install -g eclintECLint is a code validation or correction tool that does not respect the parameters defined in
.editorconfig. It also deduces the parameters of the existing code. See the [EditorConfig Project] (http://editorconfig.org/) for more details on the.editorconfigfile.$ eclint infer -ir *" ./test/*.js "> .editorconfigfor automatic creation of the .editorconfig file respecting the rules of all test.js files.The output of the command should look like this:
`` `
root = true
[*]
charset =
indent_style = space
indent_size = 2
trim_trailing_whitespace = true
end_of_line = lf
insert_final_newline = true
max_line_length = 110
`` `