Context
Discovered in #62: ReviewCanvasStatePlanner.rawDiff joins all turn diffs with \n. When multiple turns edit the same file, this produces concatenated unified diff blocks for the same path. The diff parser/renderer may handle this correctly (showing each turn's changes separately), but it hasn't been verified.
Questions
- Does the diff renderer correctly parse multiple diff blocks for the same file path?
- Should the review UI merge/squash same-file diffs across turns into a single coherent diff?
- Should the per-turn view be the default, with cumulative as an option?
- Do we properly capture/show the diff lines in the file and not make up line numbers at different indexes?
Files
OrbitDockNative/OrbitDock/Views/Review/ReviewCanvasStatePlanner.swift
- Diff parsing/rendering code
Acceptance Criteria
- Verify the current behavior with a multi-turn same-file edit scenario
- Document the intended behavior
- Fix if the renderer produces confusing output
Follow-up from #62: I_kwDORFu4Vs71S6MD
Context
Discovered in #62:
ReviewCanvasStatePlanner.rawDiffjoins all turn diffs with\n. When multiple turns edit the same file, this produces concatenated unified diff blocks for the same path. The diff parser/renderer may handle this correctly (showing each turn's changes separately), but it hasn't been verified.Questions
Files
OrbitDockNative/OrbitDock/Views/Review/ReviewCanvasStatePlanner.swiftAcceptance Criteria
Follow-up from #62: I_kwDORFu4Vs71S6MD