Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Allow for .editorconfig file to be placed in a config folder but configure parent root #342

Open
mainframenzo opened this issue Nov 29, 2022 · 1 comment

Comments

@mainframenzo
Copy link

I am woefully trying to move all of my configuration files to a folder in my source code called config. I would also like to place the .editorconfig file in this folder. I would then probably need to configure the plugin by saying that the .editorconfig file in ./config is actually in charge of configuring all files in ./, possibly by modifying it to have root = ../.

I do not think this is possible today? Please consider something like it as a feature request? Thank you!

@dserodio
Copy link

dserodio commented Apr 25, 2023

I don't think it will be supported because this is part of the spec:

Where are these files stored?

When opening a file, EditorConfig plugins look for a file named .editorconfig in the directory of the opened file and in every parent directory. A search for .editorconfig files will stop if the root filepath is reached or an EditorConfig file with root=true is found.

EditorConfig files are read top to bottom and the most recent rules found take precedence. Properties from matching EditorConfig sections are applied in the order they were read, so properties in closer files take precedence.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants