You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When adding a new workspace folder, the diagnostics should show correctly.
Actual Behaviour
The opened file for the new workspace contains tons of incorrect diagnostics, like undefined global require.
Reproduction steps
Edit a file that is not part of any workspace.
In Neovim, this will start a server with rootPath, rootURI and workspaceFolders all nil.
Any diagnostics will be properly shown for the file.
Now open a file that is part of a workspace.
Neovim will send a workspace/didChangeWorkspaceFolders width the new folder.
The server sends a workspace/diagnostic/refresh to the client.
Neovim then receives a bunch of diagnostics for the newly opened document that are all wrong. Things like Undefined global require.
After making a single file edit, diagnostics are correctly show.
How are you using the lua-language-server?
NeoVim
Which OS are you using?
Linux
What is the issue affecting?
Diagnostics/Syntax Checking
Expected Behaviour
When adding a new workspace folder, the diagnostics should show correctly.
Actual Behaviour
The opened file for the new workspace contains tons of incorrect diagnostics, like
undefined global require
.Reproduction steps
Edit a file that is not part of any workspace.
In Neovim, this will start a server with
rootPath
,rootURI
andworkspaceFolders
allnil
.Any diagnostics will be properly shown for the file.
Now open a file that is part of a workspace.
Neovim will send a
workspace/didChangeWorkspaceFolders
width the new folder.The server sends a
workspace/diagnostic/refresh
to the client.Neovim then receives a bunch of diagnostics for the newly opened document that are all wrong. Things like
Undefined global require
.After making a single file edit, diagnostics are correctly show.
Additional Notes
Related: neovim/nvim-lspconfig#2355
Log File
The text was updated successfully, but these errors were encountered: