✨ Show Code Structure when Scrolling (aka Sticky Headers)
@lassevonpfeil ya está trabajando en esto.
Desde el 21/8/2025.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Description
When working in long source files, it's easy to lose track of which class, function, or structural block you're currently in while scrolling. A helpful enhancement would be to show a floating indicator or sticky header that displays the current code structure as you scroll through the file.
Proposed Behavior
- While scrolling, a temporary overlay or sticky header appears, showing the current structural context (e.g., class, function, namespace).
- The indicator updates in real-time based on scroll position.
- The indicator fades out after scrolling stops or once the user re-engages with the editor.
Implementation Notes
- We can leverage the existing Tree-sitter integration to identify and display the current structure based on the syntax tree.
- This could tie into the same symbol parsing used for outline views or breadcrumbs, minimizing duplication.
Benefits
- Improves orientation when navigating large files.
- Reduces mental overhead by keeping context visible.
- Useful for both reading and editing code, especially in deeply nested files.
Additional Context
This behavior would be especially valuable during code review, debugging, or when working in unfamiliar codebases. It could be made optional in preferences.
- https://twitter.com/a_grebenyuk/status/1534359760308424711?s=21&t=Ok1RPHZ0s8iMU6Bf3HYJyA
- https://learn.microsoft.com/en-us/visualstudio/ide/editor-sticky-scroll?view=vs-2022
Screenshots
https://github.com/user-attachments/assets/36920923-bfd8-45f1-a63f-9b7873f4de6e
- Lenguaje dominante
- Swift
- Estrellas
- 720
- Forks
- 162
- Métricas de merge de PR
- Sin PR fusionados en 30 d
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.
Más de CodeEditApp/CodeEditSourceEditor
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
CodeEditApp/CodeEditSourceEditor#377 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
CodeEditApp/CodeEditSourceEditor#376 · 1 comentario ·
-
Dificultad 1/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 3/5 1-2 días Aptitud para principiantes 68/100
CodeEditApp/CodeEditSourceEditor#378 · 1 comentario ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 32/100
Todos los issues de CodeEditApp/CodeEditSourceEditor
Issues similares
-
The correction-threshold rationale says 17 restraint cases collide; the current corpus has 16 Abiertoarea:dictation documentation P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
uttrflow/uttrflow-swift#1180 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
OneBusAway/onebusaway-ios#1451 ·
-
enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100