Open matthew-dean opened 7 years ago
The file is not supposed to be changed by editors. However, since they are settings specific to an editor, it should have its own formats and you can pass them to your colleagues or store for yourself.
The file is not supposed to be changed by editors
Hmm...well, that's bizarre. An IDE can't provide an GUI with selectable options that get saved to .editorconfig
? Seems to really limit this format's usefulness and user-friendliness. If IDEs should supposedly read from this, seems like they should be able to then update it based on changing those options in the IDE. Otherwise, what's the point?
@matthew-dean I didn't use the correct words. It should be "if you have GUI support, not all features can be supported".
For example, You can have hierarchical structure of .editorconfig
files. You can have [*.{java,cpp}]
first, then specifying some details for [*.java]
later on in an .editorconfig
file in a subdirectory. Now you updated some options for java files. Which .editorconfig
should the GUI program update then? Similarly, we can specify regular expressions that represent partially overlapped sets of file names in two different sections. In this case, which one should be updated then?
Of course, if specifying file extensions only is the only thing you need, we can make a GUI program for that.
The spec allows for Domain Specific Settings
https://github.com/editorconfig/editorconfig/wiki/EditorConfig-Properties
The new .NET compiler/language service (roslyn) makes use of this for instance.
https://docs.microsoft.com/en-us/visualstudio/ide/editorconfig-code-style-settings-reference
Is there no extensibility in the
.editorconfig
file for IDEs to store custom settings? If there is extensibility for the format, where is that defined?