Hi EditorConfig developers and contributors
I’m a Program Manager on the Visual Studio Editor team. In response to strong customer support for the feature (see *https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/6146845-support-editorconfig* <https://visualstudio.uservoice.com/forums/121579-visual-studio-2015/suggestions/6146845-support-editorconfig> for example), we’re looking at providing all-new, native support for EditorConfig in the core Visual Studio product in a future release. We would aim to make the new EditorConfig support in Visual Studio propagate settings to VS in a manner that is more flexible and usable than what is currently possible for a VS extension. In addition, we’re planning work to provide smart support for other coding convention settings in our language services, and we’d like to leverage EditorConfig to express a (potentially large) number of such settings, via domain-specific entries in an EditorConfig file. We would want to do so in a manner that does not cause any trouble or collisions for other EditorConfig implementations (see my colleague Oleg’s *a conversion on editorconfig mail list* <https://groups.google.com/forum/#!topic/editorconfig/7w9BmR8LBmU>), so for those settings, we’d want to follow what seems to be the normal pattern of editorname_settingname. I wanted to reach out to the EditorConfig community at this stage, and ask: 1. Is adding (potentially large) numbers of custom settings to the format for our purposes reasonable? 2. Are there particular ways you’d prefer us to work with the format as we do this? Thanks in advance for your commentary and help, Regards Mark Wilson-Thomas Program Manager, Visual Studio Editor Team -- You received this message because you are subscribed to the Google Groups "EditorConfig" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/editorconfig. For more options, visit https://groups.google.com/d/optout.
