Question 1

How to set up workspace-diagnostics.nvim with lazy.nvim for automatic diagnostics?

Accepted Answer

Install the plugin via lazy.nvim and integrate it into your LSP setup by calling populate_workspace_diagnostics in the on_attach function for each LSP client, as shown in the README's usage example. This ensures diagnostics are populated automatically when servers attach.

Question 2

Does workspace-diagnostics.nvim work with all Language Server Protocol servers?

Accepted Answer

It works with most LSP servers, but some may not advertise supported filetypes, requiring you to explicitly add filetypes in the client setup, as mentioned in the configuration section. Compatibility depends on the server's adherence to LSP standards.

Question 3

How does workspace-diagnostics.nvim compare to other Neovim diagnostic plugins like null-ls or trouble.nvim?

Accepted Answer

workspace-diagnostics.nvim focuses specifically on extending LSP diagnostics to all project files, while null-ls provides alternative diagnostic sources and trouble.nvim offers a UI for displaying diagnostics. It complements rather than replaces these tools, but it's unique in its project-wide LSP coverage.

Question 4

What are the performance implications of using workspace-diagnostics.nvim on a large codebase?

Accepted Answer

Scanning all files for diagnostics can slow down Neovim, especially with large repositories or inefficient LSP servers. The plugin doesn't throttle or cache results by default, so users might experience delays during population, though this can be mitigated with manual triggering.

Question 5

Can I customize which files are scanned by workspace-diagnostics.nvim?

Accepted Answer

Yes, you can configure a custom workspace_files function in the setup to return a list of project files, overriding the default git ls-files. This allows filtering out irrelevant files or adapting to non-git projects.

Question 6

How to handle LSP clients that don't advertise filetypes with workspace-diagnostics.nvim?

Accepted Answer

You need to explicitly add filetypes when setting up the LSP client, as shown in the README configuration example for roslyn. This ensures the plugin can filter files correctly, though it adds extra steps to your setup.

workspace-diagnostics.nvim

What is workspace-diagnostics.nvim?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions