Multiple editorconfig files.

[cyraid]

I don't know if it's working to have a .editorconfig in a sub folder and have the *.cs use those rules? I don't have root = true

[nbarbettini]

I'm interested in this too. This doesn't seem to work well in VS Code or in Visual Studio itself.

[cyraid]

Nice! Yes, I'll state the reasoning real quick (for my case) before someone comes in and says "Why would you want that?". I have another library I'm using (very common when using Unity for example), and it doesn't match the code style. So now you have tooonnnnsss of errors that pop up from someone elses code style. When you could have easily put a new editorconfig file in that folder (or if it comes with it's own). That is the meaning of the 'root' boolean flag is it not?

[nbarbettini]

That's my understanding, but the docs on .editorconfig seemed a little vague on that.

In my case, I have a monorepo containing a client (written in TS/React) and a server (C#). There is a top-level .editorconfig for JavaScript stuff, and I want the .editorconfig in the server folder to change some of those options to my C# conventions. That setup works OK in Visual Studio but not great in Visual Studio Code.

[smarts]

I've run into this too with a monorepo. Here's how I ended up here:

• enable EditorConfig support + Roslyn analyzers for OmniSharp in VS Code
• enter a simple rule to prefix instance fields with _
• see that
  1. analyzing projects takes long enough for the feature to stop being useful
  2. the "Show fixes" helper in VS Code does not use the prefix when implementing a field for a new constructor parameter
• because of i, attempt to use a non-root .editorconfig file so that maybe the analyzers will only run for the projects in that directory

It seems that OmniSharp was still analyzing all projects instead of just the ones in the same directory (or in subdirectories) as the .editorconfig file that changed.
Does OmniSharp support multiple .editorconfig files?