microsoft / microsoft/vscode-pull-request-github
Folder diff view
Personne n'a encore pris cette issue.
- Langage dominant
- TypeScript
- Étoiles
- 2.6k
- Forks
- 796
- Merge moyen
- 1 j 4 h
- PR mergées (30 j)
- 46
Description
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!
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Piste de recherche
Aucun fichier ni test n’est nommé. Commencez par localiser la vue de diff unifiée existante « Changes in Pull Request » ainsi que les actions au survol ou du menu contextuel de l’arborescence des fichiers. L’implémentation doit inclure une action sur les dossiers qui ouvre un diff unifié limité à ce dossier et permet de marquer le dossier comme révisé.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- github, typescript, vscode
- Domaine
- developer-experience, tooling
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100