detect-newline is making my git diffs look bad

[TheBrenny]

There was a decision made to use detect-newline in issue #137 which was subsequently merged in #153.

This is handy, but it would be nice to override this setting to be able to enforce \n or \r\n across all contributers. Here's a screenshot of what my git diffs look like for context:

[pstanton]

Every time my colleague builds or I build there is a new commit on our "map" file because of line ending characters. we NEED a way to force it to use a consistent scheme always. I personally would choose \n.

[TheBrenny]

A good workaround for now is to use git's config option core.autocrlf. Then use VSCode to set the line ending to be LF or CRLF.

> git config core.autocrlf false

[pstanton]

A good workaround for now is to use git's config option core.autocrlf. Then use VSCode to set the line ending to be LF or CRLF.

Thanks, but neither applicable for my project.