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
Using the latest master branch (https://github.com/julia-vscode/LanguageServer.jl/tree/0da181a8e48da14c2ac46519311e01352c7c6fca) I noticed that the optional version property of the PublishDiagnosticsParams is always set to 0. As a result, the client likely rejects to update the diagnostics which are shown in the editor UI due to outdated document version. In other words the diagnostics from the state when a file was initially opened are shown in the editor, but after that they never change.
For example, the client sends textDocument/didChange like
I assume this bug was introduced with the JuliaWorkspaces, and is perhaps caused by drive letter casing of URIs not being handled correctly (just a guess), because otherwise you would have very likely already noticed it in VSCode.
The text was updated successfully, but these errors were encountered:
Using the latest
master
branch (https://github.com/julia-vscode/LanguageServer.jl/tree/0da181a8e48da14c2ac46519311e01352c7c6fca) I noticed that the optionalversion
property of the PublishDiagnosticsParams is always set to0
. As a result, the client likely rejects to update the diagnostics which are shown in the editor UI due to outdated document version. In other words the diagnostics from the state when a file was initially opened are shown in the editor, but after that they never change.For example, the client sends
textDocument/didChange
likethen the server sends
textDocument/publishDiagnostics
withI assume this bug was introduced with the JuliaWorkspaces, and is perhaps caused by drive letter casing of URIs not being handled correctly (just a guess), because otherwise you would have very likely already noticed it in VSCode.
The text was updated successfully, but these errors were encountered: