Colby Mchenry 290e03f7bc fix(explore): pin only the same-named file that defines the symbols a query names (#2071) ...

A bare basename several directories share (`editorOptions.ts`, `worker.rs`,
`compiler.py`) pinned every match, and the matches split the pinned
reservation: on vscode `editorOptions.ts clampedInt cursorStyleToString
cursorStyleFromString` gave the file holding all three 8,626 chars, against
15,181 without the path, and spent the rest on a workbench helper defining
none of them.

Path extraction now takes an injected `symbolFiles` lookup (the module stays
DB-free, like `existsOnDisk`). When a span matches several files, the matches
defining a precise symbol token the query names (camelCase, PascalCase,
snake_case, qualified — the seeder's NL-stopword shape test) are pinned and the
rest set aside; the summary line names them. When no match defines one, or
every match does, the span resolves exactly as before. The same test resolves
a basename shared past the ambiguity budget (django's `models.py`) when it
narrows into budget, and a line anchor binds once the span narrows to one file.

Replay of 196 queries over 8 indexed repos, main vs this branch: every
unambiguous pin is byte-identical (38 unique basenames, 13 dir/basename, 8
file:line, 38 earlier-sweep path queries), as are 26 path-free queries, 13
where every match defines a named symbol and 8 naming no symbol. All 52
changed responses are shared basenames — named FULL 207 -> 231 (11 up, 0 down), named lines 6,045 -> 7,577,
none over 25K.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-09-28 08:03:11 +00:00

..

identifier-segments.ts

fix(explore): accurately resolve query file paths and find camelCase symbols

2026-08-20 09:10:07 -07:00

query-parser.ts

feat(search): field-qualified queries (kind:/lang:/path:/name:) + fuzzy typo fallback (#131)

2026-05-07 20:35:49 -05:00

query-paths.ts

fix(explore): pin only the same-named file that defines the symbols a query names (#2071)

2026-09-28 08:03:11 +00:00

query-utils.ts

feat(steps): cross-tier channels — a client's fetch onto its own route, queue jobs onto consumers, bus and socket events onto handlers

2026-08-28 14:31:01 -05:00