Add explicit test for newline-preservation #486
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
#485 reported that the BFG wasn't preserving CR/LF newlines when using `--replace-text` (even modifying newlines on unaffected files). This commit adds some a couple of explicit tests, verifying that the BFG does indeed preserve newlines.
rtyley
force-pushed
the
add-explicit-test-for-newline-preservation
branch
from
47c30fb to
389ab05
Compare
Closed
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.
Issue #485 reported that the BFG wasn't preserving CR/LF newlines when using
--replace-text(even modifying newlines on unaffected files).This commit adds a couple of explicit tests, verifying that the BFG does indeed preserve newlines.