Add specific .editorconfig file for each specific style linting

[DrSensor]

What problem does this feature solve?

This feature will configure autocomplete to a specific style in any IDE that support .editorconfig file. For example when choosing linter to use AirBnB or StandardJS style, it will generate editorconfig with that specific style.

Just info : content in editorconfig file is universal and can be applied to any IDE.

What does the proposed API look like?

Prompt

Create editorconfig? Y/n

Or just create it without prompting.

[psg2]

Could I start working on this feature?

[kazupon]

Sure! 🙂

[psg2]

Just to be clear about the proposal.

During the prompt both on the create command and on the invoke with cli-plugin-eslint, it should ask if the user wants to create an editorconfig file if the Airbnb or the Standard option was chosen?

And the config files should be the ones contained in the repositories:

• Airbnb
• Standard

Or is it best to create the editorconfig file without prompting?

I'm thrilled to work on this feature, both because I'm enjoying Vue so much and because it will be my first real open source contribution.

[hsxfjames]

I vote for create without prompting, so that peoples do not have to worry about too much options.

[psg2]

What should happen during invoke if the user already has an editorconfig file?

[elevatebart]

I would love to keep consistency with the choosen linters.
For instance, if I choose eslint preset AirBnB, I keep AirBnB for the .editorconfig.
And since @vue/cli supports prettier preset for eslint we should try to implement it as well.

Regarding the prompt, @psg2 I would use the linter if there is one and ask for a preset if not.

What do you think ?

[defnorep]

Also might be prudent to think about what happens when TypeScript is enabled. You can use either ESLint or TSLint on TypeScript projects. There are AirBnb presets for both TSLint and ESLint too. Do we require some kind of abstraction above ESLint and TSLint with a negotiator behind the scenes?

[psg2]

@elevatebart I'm sorry, but I didn't understand what you meant by "And since supports prettier preset for eslint we should try to implement it as well.".

Could you explain one more time?

@Daekano I think there's no adjustment considering Typescript. Because the editorconfig from Airbnb and standard would remain the same. And the other linting options doesn't have default editorconfig files.
But as for the cli, maybe there should be options for TSLint + Airbnb, TSLint + Standard, etc... Instead of just default TSLint and various ESLint options when Typescript is chosen.

[elevatebart]

@psg2 the Prettier preset for eslint is a little different from AirBnB and Standard, for instance using prettier uses double quotes instead of single quotes.
If you choose one of the 2 presets that you quote, it will conflict with prettier.

Have a look at this repo and I hope you will understand better.
https://github.com/prettier/eslint-config-prettier

If not, please pm me on twitter @bartledoux.
I am interrested in helping you with this task.

[psg2]

@elevatebart I understand that. But eslint-config-prettier doesn't provide an editorconfig file. So if the users choose eslint + prettier as the linter option, it should not generate an editorconfig file and would stay as it is today.
Or should we declare an editorconfig file for that option?

[elevatebart]

Indeed, my bad, the whole purpose of prettier is specifically to avoid the need of a config file.