microsoft / microsoft/vscode-pull-request-github
Folder diff view
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 2.6k
- Forks
- 795
- Ø Merge
- 1 T. 4 Std.
- Gemergte PRs (30 T.)
- 46
Beschreibung
Thank you all for creating such a great extension! This has become my go-to tool for GitHub PR reviews. It's a much better alternative to the GitHub web interface in my opinion.
I'd like to suggest a feature that would significantly improve my workflow and potentially others' as well. The existing "Changes in Pull Request" unified diff view is an excellent way to quickly review changes across the entire PR. However, it would be incredibly helpful to have a folder-level unified diff view with the same layout.
Often during code reviews, certain folders contain many small, straightforward changes (e.g. such as during refactors or bulk updates) while others contain more involved changes. Currently, clicking through each individual file to review small changes is more cumbersome than scrolling through the consolidated PR diff view. However, since the existing unified view displays all files at once, it's hard to isolate just the easy-to-review files from the more complex ones.
The ideal solution would be to add a hover action or context menu to each folder in the file tree, allowing users to open a unified diff view that shows only the files within that folder. This would allow reviewers to quickly scroll through related changes, mark the entire folder as reviewed, and move on strategically.
Thank you again for the amazing work on this extension!
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Es werden keine Dateien oder Tests genannt. Beginne damit, die vorhandene einheitliche Diff-Ansicht „Changes in Pull Request“ sowie die Hover- oder Kontextmenü-Aktionen des Dateibaums zu finden. Die Umsetzung sollte eine Ordneraktion umfassen, die einen auf diesen Ordner begrenzten einheitlichen Diff öffnet und das Markieren des Ordners als überprüft unterstützt.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- github, typescript, vscode
- Bereich
- developer-experience, tooling
- Issue-Typ
- Feature
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 35/100