EditorConfig helps developers define and maintain consistent coding styles between different editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readable and they work nicely with version control systems.
What’s an EditorConfig file look like?
Example file
Below is an example .editorconfig file setting end-of-line and indentation styles for Python and JavaScript files.
# EditorConfig is awesome: https://EditorConfig.org
# top-most EditorConfig file
root=true# Unix-style newlines with a newline ending every file
[*]end_of_line=lfinsert_final_newline=true# Matches multiple files with brace expansion notation
# Set default charset
[*.{js,py}]charset=utf-8# 4 space indentation
[*.py]indent_style=spaceindent_size=4# Tab indentation (no size specified)
[Makefile]indent_style=tab# Indentation override for all JS under lib directory
[lib/**.js]indent_style=spaceindent_size=2# Matches the exact files either package.json or .travis.yml
[{package.json,.travis.yml}]indent_style=spaceindent_size=2