A Neovim plugin that populates LSP diagnostics for all project files, not just opened ones.
workspace-diagnostics.nvim is a Neovim plugin that extends Language Server Protocol (LSP) diagnostics to all files in a project, not just those currently open in buffers. It provides a comprehensive view of code issues across the entire workspace, improving code quality awareness and debugging efficiency by overcoming the default LSP limitation.
Neovim users who work with LSP servers and want to see diagnostics for their entire project, such as developers in codebases with many files or those conducting code reviews and maintenance tasks.
Developers choose this plugin because it automatically populates diagnostics for all relevant project files, offering a holistic view of project health without manually opening each file, with configurable file listing and filetype-aware filtering for precision.
Populate diagnostics for all projects files, not just opened ones.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Populates LSP diagnostics for every file in the project, not just open buffers, overcoming the default LSP limitation and providing a holistic view of code issues.
Can be triggered automatically when an LSP client attaches to a buffer, ensuring diagnostics are always up-to-date without manual intervention.
Supports both automatic population on attach and manual triggering via keybindings, offering control over when diagnostics are updated for on-demand scanning.
Allows customization of the project file list with a default of git ls-files, adaptable via a custom function for tailored project structures.
When triggered manually, it only populates diagnostics for files sharing the current buffer's filetype, which can be restrictive in mixed-language projects, as noted in the README caveat.
Some LSP clients don't advertise supported filetypes, forcing users to explicitly specify them in the setup, adding configuration overhead and potential for misconfiguration.
Scanning all project files for diagnostics can introduce latency and increased resource usage, especially in large repositories or with slow LSP servers, which isn't addressed in the README.