ESLint configuration fix to support both UNIX and WINDOWS line-endings #1
Conversation
This file contains hidden or 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
paulsmirnov
approved these changes
Apr 4, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
General idea
Currently ESLint config enforces UNIX style line-endings. That causes thousands of warnings when building solution using Windows. This Pull Request introduces platform independant approach:
Force GIT to handle line-endings natively for each client platform
Make ESLint check that all line-endings are in the same notation
Changes summary
.gitattributes - Added configuration that enables the conversion of CRLF to LF and backward by GIT client
.eslintrc.js - changed the method of EOL style selecting