.editorconfig supports domain specific properties: https://github.com/editorconfig/editorconfig/wiki/EditorConf....
Its encouraged that other extensions/tooling take a dependency on .editorconfig to introduce their own configuration.
Interesting. I'll take a look to see what domain specific properties exist.
Typically those are done using configuration files of code-checking tools, such as .jshintrc[1] or .pylintrc.
I guess I just figure these two are sort of overlapping. If you use .jshintrc why do you need this tool?
(The neat idea being: if a project has many languages, you can share code conventions for all of them in one place.)
Re:EditorConfig
by michaelmior on Thursday October 16, 2014 @09:21AM
(#8464705)
The nice thing about EditorConfig is that it fixes some problems before they occur instead of requiring you to manually fix things after running a linter (e.g. spaces vs tabs)
What are you looking to do with "language styles" that you can't do based on file extension?
There is JSCS for Javascript: https://github.com/jscs-dev/node-jscs#options
I like this, but the list of supported properties seems pretty short. I can see there might be some difficulties making it language-aware since the file formats are simple globs, but maybe you could say something like:
and somewhere describe that language_style in more detail.