fix(blast): preserve precise ranges with custom Git diff prefixes - #390
cookerpapa wants to merge 1 commit into
Conversation
🌱 graft blast radius1 area changed → 2 areas can be affected. 2 dependent symbols, depth 2. flowchart TB
A0(("Pull Request Review<br/>1 symbol"))
A1(("Blast CLI<br/>1 symbol"))
classDef reached fill:#D9EDF3,stroke:#3AA7C9,stroke-width:1.5px,color:#0E313C;
class A0,A1 reached;
Who knows this code — 1 person across 3 areas
Ownership is git history over each area's own files, weighted towards recent work (120-day half-life). Merge commits and bots are dropped, and you are dropped from your own PR. A name with no All 2 dependent symbols, grouped by areaPull Request Review — 1 symbol in 1 file
Blast CLI — 1 symbol in 1 file
Test signal per changed area — 1 ✗Reached = a node under a test path has a resolved edge into the changed symbol. It undercounts anything called indirectly — through a CLI, a spawned process or a dynamic import — so read a low ratio as “look here”, never as a coverage gate.
Open the interactive graph → — click an area to see its dependent symbols at file:line. |
Git prefix settings can prevent patch paths from matching changed files, causing blast to lose line ranges and fall back to whole-file seeds.
Pin a/ and b/ prefixes for the internal patch command. User configuration is preserved. Tests cover working-tree, explicit-base, and last-commit comparisons, plus precise CLI symbol seeds.
Fixes #369.
Validation: