EditorConfig plugins can be developed by using one of the EditorConfig core libraries. The EditorConfig core libraries accept as input the file being edited, find and parse relevant .editorconfig files, and pass back the properties that should be used. Please ignore any unrecognized properties and property values in your editor plugin for future compatibility, since new properties and permitted values will be added in the future. Currently there is a C library, a Python library, a JavaScript library, two Java libraries (EditorConfig Core Java Library and ec4j), a Lua library, a .NET library, a Ruby library, and a Go library.
+ EditorConfig plugins can be developed by using one of the EditorConfig core libraries.
+ The EditorConfig core libraries accept as input the file being edited, find and parse relevant .editorconfig files, and pass back the properties that should be used.
+ Please ignore any unrecognized properties and property values in your editor plugin for future compatibility, since new properties and permitted values will be added in the future.
+
+ EditorConfig core libraries exist for many programming languages: +
+If you are planning on creating a new plugin, use the mailing list to let us know so we can help out and link to your plugin once it's created. If you plan on using one of the EditorConfig cores as a library or command line interface, the C library documentation, Python library documentation or Java library documentation may be helpful.
More details can be found on the Plugin-How-To wiki page.