Workspace diagnostics unavailable, only buffer diagnostics shown

[thraizz]

Hi, and sorry for the possibly wrong repo for this question, iwas unsure if this is ts-utils or null-ls related.

I am currently trying to set up my nvim lsp for typescript and while everything works well in one buffer (completion, formatting, diagnostics etc. (even though i am not sure if I should use both tsserver+nvim-lsp-ts-utils and null_ls)), I cannot get workspace wide diagnostics to work.
It seems like this has something to do with tsserver only attaching to open buffers, and not respecting eslint_d's workspace diagnostic.
My lsp config configures the tsserver first and then null-ls, i've experimented with the available options but to no success. My current config can be seen here: https://github.com/thraizz/dotfiles-nvim/blob/master/lua/lsp.lua
What do I need to change to get workspace diagnostics available?
Thank you for your great work!

[jose-elias-alvarez]

I think there might be some confusion - tsserver is an actual language server, and in this case null-ls is just a wrapper around command-line tools, so there won't be any interaction between them (nor would there be any interaction between two actual language servers). There's no issue with running a language server + null-ls, but you'll have to configure them separately.

Workspace diagnostics need to be supported at the language server level, and typescript-language-server does not yet have support (there's an open PR). Some null-ls sources do support workspace diagnostics, but eslint_d is not one of them. It's definitely possible to add support, but generally I've been guiding people to the ESLint language server, which is a better option in 99% of cases. (Unfortunately, that server also doesn't support workspace diagnostic, and a PR to add support was closed last year due to unresolved issues).

[thraizz]

Thanks, this solved my confusion! 🐱