EditorConfig – file format for defining coding styles and text editor plugins
1–10 of 32 posts
Re: EditorConfig – file format for defining coding styles and text editor plugins
#2At least in the JavaScript world, this was a lovely thing to have. Now we have linters which are even better! Still nice to include this so that all collaborators don't need to modify their editors to jump in!
Re: EditorConfig – file format for defining coding styles and text editor plugins
#3At least in the JavaScript world, this was a lovely thing to have. Now we have linters which are even better! Still nice to include this so that all collaborators don't need to modify their editors to jump in!
It's the simple cross editor convenience this brings that really appeals to me.
Re: EditorConfig – file format for defining coding styles and text editor plugins
#4Before clicking on the link, I thought "Oh, just another attempt at standardizing editor preferences from a file in a repo." But looking at their list of editors which natively support EditorConfig and the list of plugins for editors which don't, this is far better support than I imagined. This is it! Problem solved.
Re: EditorConfig – file format for defining coding styles and text editor plugins
#5I made this a standard for all my engineers years ago. anything I can do to automate consistency and "correctness" in coding style and let my team focus on doing the real work
Re: EditorConfig – file format for defining coding styles and text editor plugins
#6At least in the JavaScript world, this was a lovely thing to have. Now we have linters which are even better! Still nice to include this so that all collaborators don't need to modify their editors to jump in!
and now we have https://prettier.io/docs/en/why-prettier.html we can automatically enforce and fix all these style rules
Re: EditorConfig – file format for defining coding styles and text editor plugins
#7EditorConfig is awesome, especially for a distributed remote team. I've standardized everyone whom I ever worked with few initial project settings and EditorConfig is such one must-do item. Been using it (I think) for the past 5 years or so.
Re: EditorConfig – file format for defining coding styles and text editor plugins
#8At least in the JavaScript world, this was a lovely thing to have. Now we have linters which are even better! Still nice to include this so that all collaborators don't need to modify their editors to jump in!
and now we have https://prettier.io/docs/en/why-prettier.html we can automatically enforce and fix all these style rules
I haven't used prettier but eslint can also fix style
Re: EditorConfig – file format for defining coding styles and text editor plugins
#9The companion would be eclint in order to lint as part of a git hook or CI test run
Re: EditorConfig – file format for defining coding styles and text editor plugins
#10Before clicking on the link, I thought "Oh, just another attempt at standardizing editor preferences from a file in a repo." But looking at their list of editors which natively support EditorConfig and the list of plugins for editors which don't, this is far better support than I imagined. This is it! Problem solved.
Honestly I don't think much is solved by EditorConfig.
I mean, the idea is great, but the small amount of parameters supported makes it pretty much useless. Indentation character and size, line termination, ... and that's all. I would need a hundred of these (like clang-format, yapf, etc have) to switch to EditorConfig. Unfortunately, looking at the commit log frequency, I doubt EditorConfig will ever have more than the 10 or so parameters that it already have.