-
-
-
-
Previous Value Current Value Open
Closed
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Issue Votes (0)
| Previous Value | Current Value |
|---|---|
Open | Closed |
| Type |
New Feature
|
| Priority |
Normal
|
| Assignee | |
| Labels |
No labels
|
Motivation
OneDev diffs show changed lines and expandable unchanged lines, but they do not identify the enclosing class, function, or method. In a long file, reviewers can therefore see what changed without knowing where the change belongs. The problem is more pronounced when the old and new sides correspond to different symbols, such as when code is moved or a method is renamed.
This request follows the finalized design discussion in #3089.
Current UX
Given code such as:
the reviewer must navigate away from the change or expand surrounding lines to discover that it belongs to
AccountService.reconcileAccounts.Proposed UX
Show both per-hunk context and sticky context. Old and new revision contexts remain independent because they may refer to different symbols.
Split view
Unified view
Desired behavior
OLDandNEW) that update independently.