microsoft / microsoft/vscode-pull-request-github
Folder diff view
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2.6k
- Forks
- 795
- Merge medio
- 1 d 4 h
- PR fusionados (30 d)
- 46
Descripción
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!
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
No se nombran archivos ni pruebas. Empieza por localizar la vista de diff unificada existente “Changes in Pull Request” y las acciones al pasar el cursor o del menú contextual del árbol de archivos. La implementación debería incluir una acción para carpetas que abra un diff unificado limitado a esa carpeta y permita marcarla como revisada.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github, typescript, vscode
- Área
- developer-experience, tooling
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 35/100