Open djc opened 1 year ago
I know you are dealing with an enormous amount of requests/Issues and I really appreciate your work! I wanted to ask if this Issue is somewhere on the roadmap? This is something that would make my DX significantly better. I am going all-in on Zed but this is something I miss from VSCode.
FWIW, this seemed to be one of the most popular replies in this recent Twitter thread:
please add this
Yes this would be a fantastic add.
I would greatly benefit from this feature
Same here, our toolchain creates and modify files automatically, sometimes it's hard to know we have an issue before compile time. I'm absolutely in love with Zed and it's the last remaining feature that would make zed my daily driver !
Same issue, the only two missing parts for me are the source control tab and this one. I'm fine not having the source control tab any time soon, but not seeing errored files in the tree view and in the opened tabs list doesn't allow me to switch to Zed today.
If that could help, Zed has an outline view which can be opened for any [multi] buffer.
There's no coloring, but if you open a diagnostics multi buffer it will show all files with errors in a tree:
If that could help, Zed has an outline view which can be opened for any [multi] buffer.
There's no coloring, but if you open a diagnostics multi buffer it will show all files with errors in a tree:
This is definitely helpful, but just like a file is yellow if it has a change in it... having it red is immensely helpful. I don't have the screen real-estate to keep this window open -- love Zed, but this is the thing I miss most about vscode
Any update on this? Or even an alpha/beta build we can use to have this feature early?
This feature is the only deal-breaker for switching to Zed...
Agreed, with large monorepos this is essential.
Check for existing issues
Describe the feature
In VS Code, I rely a lot on the explorer showing me in which files the compiler has found errors/warnings. Ideally, it would both use colors and a number of errors/warnings to indicate how badly my current state is broken.
If applicable, add mockups / screenshots to help present your vision of the feature
No response