Ensure files end with a single new line #477
Merged
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
shocklateboy92
requested changes
Nov 14, 2021
| var trimmed = 0; | ||
| for (; trimmed < Output.Length; trimmed++) | ||
| { | ||
| if (Output[^(trimmed + 1)] != '\r' && Output[^(trimmed + 1)] != '\n') |
There was a problem hiding this comment.
Does this work for Unix line endings that don't have a carriage return?
There was a problem hiding this comment.
It does, I have some unit tests for it in DocPrinterTests. I did have a copy paste error and wasn't actually testing just "\n" though.
belav
force-pushed
the
single-new-line
branch
from
b75f4b6 to
982c510
Compare
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.
closes #464