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
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.
Addresses the separator collision reported in #141.
Add an opt-in
preserveReplacementoption so characters already equal to the chosen replacement are kept instead of being folded into surrounding whitespace. This makesstep -1becomestep--1whilestep 1remainsstep-1, and keeps1952--intact. The default behavior is unchanged. Document the option and add its TypeScript declaration and regression cases. This is separate from #179, which proposes preserving arbitrary characters through strict filtering.Baseline reproduction: both
step -1andstep 1producedstep-1;1952--produced1952. Local verification: direct Mocha run passed all 46 tests; direct Node output confirmed the three expected cases and unchanged default; a TypeScript import using the new option compiled withtsc --noEmit;git diff --cached --checkpassed.