Skip to content
This repository has been archived by the owner on Oct 4, 2020. It is now read-only.

Reusing an existing configuration .editorconfig file #214

Open
cavo789 opened this issue Jun 3, 2020 · 3 comments
Open

Reusing an existing configuration .editorconfig file #214

cavo789 opened this issue Jun 3, 2020 · 3 comments

Comments

@cavo789
Copy link

cavo789 commented Jun 3, 2020

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
Copy link
Owner

jednano commented Jun 5, 2020

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

@cavo789
Copy link
Author

cavo789 commented Jun 5, 2020

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
Copy link
Owner

jednano commented Jun 5, 2020

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cavo789 @jednano