From 1efc0cb4c30c1de4eeaea97157573f688dc245fb Mon Sep 17 00:00:00 2001 From: SAY-5 Date: Mon, 11 May 2026 13:04:03 -0700 Subject: [PATCH] chore: remove em-dashes from comments --- src/core/diff/strategies/multi-search-replace.ts | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/core/diff/strategies/multi-search-replace.ts b/src/core/diff/strategies/multi-search-replace.ts index a1e69e8053..398933226b 100644 --- a/src/core/diff/strategies/multi-search-replace.ts +++ b/src/core/diff/strategies/multi-search-replace.ts @@ -13,7 +13,7 @@ const BUFFER_LINES = 40 // Number of extra context lines to show before and afte * * If the LLM forgets the newline after the separator, the run-on line * (e.g. `-------import { ... }`) ends up as the first line of the - * captured search content. The outer regex doesn't reject this — it + * captured search content. The outer regex doesn't reject this, it * just falls through, and the file-content match fails with a * confusing "63% similar" error. By detecting the malformed prefix * here we can return an actionable error instead. @@ -39,7 +39,7 @@ function detectMalformedSeparator(searchContent: string): string | null { } const tail = match[1].trim() // Allow lines that start with a literal `-` continuation (e.g. - // markdown bullets that begin with extra dashes) — they wouldn't + // markdown bullets that begin with extra dashes), they wouldn't // look like the separator-then-code shape that confuses callers. if (tail === "" || /^-+$/.test(tail)) { return null @@ -302,7 +302,7 @@ export class MultiSearchReplaceDiffStrategy implements DiffStrategy { Ensures the first marker starts at the beginning of the file or right after a newline. 2. (?