linebreak-style makes it impossible for Windows users to contribute #35
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Any project that currently uses eslint-config-xo checked out on Windows results in thousands of linter errors, making it impossible to contribute to these projects as a Windows user without nerfing the linter entirely. A better way to enforce this is not via a linter, but via a .gitattributes file (https://help.github.com/articles/dealing-with-line-endings). When you do this, Git will ensure the repo internally is LF, but on Win32 will check out files as CRLF (this is a builtin case of a clean/smudge filter)
anaisbetts
added a commit
to anaisbetts/javascript
that referenced
this pull request
Dec 28, 2016
Any project that currently uses eslint-config-airbnb checked out on Windows results in thousands of linter errors since the line endings will be CRLF, making it impossible to contribute to these projects as a Windows user without nerfing the linter entirely. A better way to enforce this is not via a linter, but via a .gitattributes file (https://help.github.com/articles/dealing-with-line-endings). When you do this, Git will ensure the repo internally is LF, but on Win32 will check out files as CRLF (this is a builtin case of a clean/smudge filter) Refs vercel/hyper#1230, xojs/eslint-config-xo#35
This was referenced Dec 28, 2016
|
@sindresorhus Working on a version that might be more amenable to Mac users: eslint/eslint#7823 |
anaisbetts
added a commit
to electron/forge
that referenced
this pull request
Jan 2, 2017
See airbnb/javascript#1224, xojs/eslint-config-xo#35, and eslint/eslint#7823 for the sad details. This doesn't completely solve the greater issue, but should at least help a little bit to ensure new Electron projects can be used on Windows
MarshallOfSound
pushed a commit
to electron/forge
that referenced
this pull request
Jan 2, 2017
See airbnb/javascript#1224, xojs/eslint-config-xo#35, and eslint/eslint#7823 for the sad details. This doesn't completely solve the greater issue, but should at least help a little bit to ensure new Electron projects can be used on Windows
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Any project that currently uses eslint-config-xo checked out on Windows results in thousands of linter errors since the line endings will be CRLF, making it impossible to contribute to these projects as a Windows user without nerfing the linter entirely.
A better way to enforce this is not via a linter, but via a .gitattributes file (https://help.github.com/articles/dealing-with-line-endings). When you do this, Git will ensure the repo internally is LF, but on Win32 will check out files as CRLF (this is a builtin case of a clean/smudge filter)
Refs vercel/hyper#1230