✨ Show Code Structure when Scrolling (aka Sticky Headers)

Aperta
#42 3 commenti 1 reazione 1 assegnatario Vedi su GitHub

@lassevonpfeil ci sta già lavorando.

Dal 21/8/2025.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

editor enhancement UI
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.

Screenshots

https://github.com/user-attachments/assets/36920923-bfd8-45f1-a63f-9b7873f4de6e

Lingua principale
Swift
Stelle
720
Fork
162
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di CodeEditApp/CodeEditSourceEditor

Tutte le issue di CodeEditApp/CodeEditSourceEditor

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.