Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use \n for line endings #147

Merged
merged 1 commit into from Aug 14, 2020
Merged

use \n for line endings #147

merged 1 commit into from Aug 14, 2020

Conversation

martijnhoekstra
Copy link

having platform-dependent line endings makes contraband behave platform dependently. That's undesirable for reproducibility and problematic in cases where contraband output is part of some VCS where people on different platforms collaborate.

fixes #122

having platfrom dependent line endings makes contraband
behave platform dependently. That's undesirable for
reproducibility
@eed3si9n
Copy link
Member

If we used \n, I'd also get flak from Windows-using companies. Shouldn't line-ending be the same as one would code by hand? The idea floated in #122 was to make line-ending configurable.

@martijnhoekstra
Copy link
Author

I guess this would create large diffs once for repos that only use windows both on local machines and CI. While I suspect that to be uncommon, I can't be sure.

If they should look the same as coded by hand, that's going to differ from person to person. I don't think many people use \r\n. Perhaps the line end should align with the most commonly used line end in the contraband file.

@eed3si9n eed3si9n merged commit 2de9394 into sbt:master Aug 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

always use \n for line breaks
2 participants