Issue 2016: edits change windows line endings to linux endings #2017
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
added 2 commits
August 17, 2025 17:00
normalizedNewString is self-explanatory, but the LineTrimmedReplacer
change makes sure an edit doesn't remove \r from the last line.
Also, I took a liberty of making LineTrimmedReplacer slightly more
concise, it was not necessary, the important part is:
if (matchString.endsWith("\r")) {
matchString = matchString.slice(0, -1)
}
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.
#2016
normalizedNewString is self-explanatory, but the LineTrimmedReplacer change makes sure an edit doesn't remove \r from the last line.
Also, I took the liberty of making LineTrimmedReplacer slightly more concise; it was not necessary. The important part is:
if (matchString.endsWith("\r")) {
matchString = matchString.slice(0, -1)
}