Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Visually integrate file status into the file tree view #3044

Open
KillingSpark opened this issue Mar 7, 2024 · 0 comments
Open

Visually integrate file status into the file tree view #3044

KillingSpark opened this issue Mar 7, 2024 · 0 comments
Labels
A-ui Area: UI rendering and interactions C-feature Category: New feature or request

Comments

@KillingSpark
Copy link

KillingSpark commented Mar 7, 2024

Describe the solution you'd like

This is a feature of vscode that I think all editors with a builtin file tree viewer should have: Visually integrate the status of the files into the file tree. Examples include:

  • the git status of the file (changed, untracked, staged, ...)
  • the LSP status of the file (errors, warnings)

This should propagate upwards through the directories, merging the states of the files in the directory in some sensible way.

Describe alternatives you've considered

A common alternative (also currently implemented in lapce, but many other editors have the same solution) is having separate views for this.

  • the file tree (to open editors)
  • the errors/warnings view that displays the files as a list with the errors contained in them (and to open editors)
  • the git view that displays the changed files as a list (open diffs and commiting)

Obviously the separated views have their usecases too, I don't think the visual integration of the latter two into the file tree would be able to replace them.

Additional context

The LSP integration would be especially useful to me when I am refactoring code or changing core concepts in a library to see how many locations would be affected by a change I am considering.

The git integration would be useful to me when I am cleaning up code with many small changes and need to decide when a changeset is getting too large so I should do a commit.

Having this integrated into one view would make it easier to do these things compared to more views necessitating switching the view (git view) or using up more screen realestate (LSP view).

I would be willing to do the legwork for this feature but before I get familiar with the codebase and start work I wanted to know if this is both wanted by the project and feasible.

@KillingSpark KillingSpark added the C-feature Category: New feature or request label Mar 7, 2024
@MinusGix MinusGix added the A-ui Area: UI rendering and interactions label Mar 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ui Area: UI rendering and interactions C-feature Category: New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants