fix(web): handle quoted string escapes correctly

Author: breken-ai

packages/web/src/features/search/parser.test.ts

@@ -72,6 +72,32 @@ describe('parseQuerySyntaxIntoIR', () => {
             });
         });
 
+        it('unescapes a backslash-escaped newline', async () => {
+            const ir = await parseQuerySyntaxIntoIR({
+                query: '"line1\\\nline2"',
+                options: {},
+                prisma,
+            });
+
+            expect(ir).toMatchObject({
+                query: 'substring',
+                substring: { pattern: 'line1\nline2' },
+            });
+        });
+
+        it('preserves backslashes before other characters', async () => {
+            const ir = await parseQuerySyntaxIntoIR({
+                query: '"C:\\temp"',
+                options: {},
+                prisma,
+            });
+
+            expect(ir).toMatchObject({
+                query: 'substring',
+                substring: { pattern: 'C:\\temp' },
+            });
+        });
+
         it('unescapes a quoted content: value', async () => {
             const ir = await parseQuerySyntaxIntoIR({
                 query: 'content:"say \\"hi\\""',

packages/web/src/features/search/parser.ts

@@ -72,12 +72,13 @@ const findLinguistLanguage = (value: string): string => {
 }
 
 /**
- * Quoted strings may contain backslash escapes (e.g. `\"`). Keyword search
- * matches patterns literally, so the escapes are resolved here. In regex mode
- * they are left in place for the regex engine to interpret.
+ * Quoted strings may escape quotes, backslashes, and line terminators. Keyword
+ * search matches patterns literally, so those escapes are resolved here. Other
+ * backslashes remain literal (e.g. in Windows paths). In regex mode escapes
+ * are left in place for the regex engine to interpret.
  */
 const unescapeQuotedString = (value: string): string => {
-    return value.replace(/\\(.)/g, '$1');
+    return value.replace(/\\(["\\\r\n])/g, '$1');
 }
 
 /**