fix: preserve leading unchanged context before the first diff hunk#321
Closed
omry wants to merge 1 commit intotomasz-tomczyk:mainfrom
Closed
fix: preserve leading unchanged context before the first diff hunk#321omry wants to merge 1 commit intotomasz-tomczyk:mainfrom
omry wants to merge 1 commit intotomasz-tomczyk:mainfrom
Conversation
Show an expandable spacer before the first diff hunk when a file has unchanged lines at the top, including zero-count unified diff cases like pure insertions or deletions. Recompute merged hunk ranges from the merged line numbers so expanded headers stay accurate after revealing leading context. Also tighten the Playwright diff-rendering spec to use the shared server.go helper and retryable spacer-count assertions.
3 tasks
Owner
|
Thank you ❤️ I've reimplemented it in #338 including support for the last diff hunk |
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
2 participants
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.
Updated UI:
Fixes #319