search

jednano / eclint

Validate or fix code that doesn't adhere to EditorConfig settings or infer settings from existing code.
MIT License
307 stars 28 forks source link

Reusing an existing configuration .editorconfig file #214

Open cavo789 opened 4 years ago

cavo789 commented 4 years ago

Hello

Sorry it probably exists but I didn't find the option: is there an option for specifying where is our existing .editorconfig file?

Is it possible to run a command like: eclint check --configuration ./../../.editorconfig *.md?

Thanks.

jednano commented 4 years ago

There's not necessarily just one .editorconfig file. Could be multiple that end up combining into the config for a particular file.

cavo789 commented 4 years ago

Hello and thank you for your answer that ... I didn't understand, sorry.

If I can precise my file and there, except if I'm wrong, it's possible to say "final=true" so the file will be only that one...

My question is to be able to reuse the .editconfig file that I'm using with Visual Studio Code and to not have to use all the existing arguments you've defined.

Is this possible?

Thanks for your help.

jednano commented 4 years ago

Go to EditorConfig.org and you’ll see root=true is the first declaration of the example file. You can read the specification for more info.