Improve VS Code diff and graph comparison experience#45
Merged
Conversation
forhappy
marked this pull request as ready for review
July 26, 2026 07:02
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
@pierre/diffs, including split/unified modes, wrapping, responsive layout, file collapsing, and raw-patch fallbackWhy
The query tabs did not clearly communicate which mode was active, raw patches were difficult to scan, and graph deltas mixed change state with community and confidence styling. Source navigation also left the cursor on the recorded last line instead of immediately below the selected range.
User impact
Users can identify the active query mode at a glance, review revision diffs in a familiar code-review layout, isolate graph changes by status, and continue editing directly below a selected graph node's source range.
Validation
graphify update .