Open johnpduane opened 3 years ago
@johnpduane I'm leaning towards not using linter as a code formatter at all and remove all formatting rules from the linter (airbnb). Add prettier rules for code formatting but don't enforce them. The team working on the project can set format on save and external contributors code can be formatted on merge.
I have a team experimenting with this repo and we are using a mix of Windows and Macs for development. If the Windows users touch any files, they get a linebreak-style error during the build portion of an
npm run serve
, for example:There are straight-forward work-arounds but I think this issue should be addressed in your default branch as I assume this could be a blocker for newer users. Here are a few options to consider:
'linebreak-style': 'off',
to the repo's .eslintrc.jsend_of_line
, see airbnb/javascript/.editorconfig for an example."files.eol": "\n"
.If you'd like me to submit a PR using any of these suggestions, I'm happy to do so.