Open bignose-debian opened 7 years ago
I have a proposed implementation, that cleans up the code base (as of current ‘master’) to conform with some standard settings, then adds the EditorConfig settings file to enforce them.
ACK, I'll look into it, maybe something can be also automated in Travis to ensure correctness. Thanks.
I don't have experience with a tool to analyse a code base and report violations from EditorConfig preferences. Maybe https://www.npmjs.com/package/@htmlacademy/check-editorconfig can help.
With many contributors, this project would IMO benefit if this code base declares an EditorConfig settings file, and conforms to basic conventions in text files.
With an appropriate EditorConfig settings file, contributors can just turn on EditorConfig in their preferred text editor to get all the right settings for this code base.