Skip to content
This repository has been archived by the owner on Jul 6, 2021. It is now read-only.

Feature Request: Workspace diagnostics #61

Open
ckipp01 opened this issue Sep 27, 2020 · 1 comment
Open

Feature Request: Workspace diagnostics #61

ckipp01 opened this issue Sep 27, 2020 · 1 comment

Comments

@ckipp01
Copy link
Contributor

ckipp01 commented Sep 27, 2020

Hello! I was wondering if it would be possible for diagnostic-nvim to also offer an option to show all workspace diagnostics instead of the buffer that it was opened from. I know for myself when I'm doing larger refactorings it's extremely helpful to see diagnostics in other places in my codebase.

Another issue I often come across is that I will have a buffer open, OpenDiagnostics, which will show me my diagnostics for the current buffer, and then I will split and open something else to fix something etc. Then I may close the original, which leaves the list open showing diagnostics for my previous buffer.

There is actually a pr for this in the nvim-metals repo, but it's a very simple implementation.

I'd love to hear your thoughts on whether or not this is something you'd consider adding to diagnostic-nvim. Thanks!

@haorenW1025
Copy link
Collaborator

Hmm I'm not very sure about this, currently I'm viewing diagnostic-nvim as a transition project before the built-in LSP has better startup configuration. I've heard that @tjdevries has been working on merging some improvement to the built-in core, so I'm thinking that this should be a feature request in the neovim repository.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants