Closed duydang2311 closed 3 years ago
Can you set "log_debug": true,
in LSP.sublime-settings
and then reopen the file and check the sublime console? I'd like to know if there are some related messages from LSP that say "ignoring unsuitable diagnostics for..."
It's looking like a regression in the new server version. Same as #78.
First of all, thank you for your time.
I've set the "log_debug": true
in Preferences: LSP Settings
and don't find any messages that say "ignoring unsuitable diagnostics for..." in the console (which is opened when pressing Ctrl+` if I am correct).
If you have identified the issue, I will test again to close this when your fix is merged and released.
Having found that your fix was merged, I updated my typescript-language-server
version to 0.6.1
but the diagnostic still not making any difference.
How have you updated exactly? The version on https://packagecontrol.io/packages/LSP-typescript is not yet up-to-date.
Oh really, I thought I just need to update my typescript-language-server
npm package version through the CLI.
No, that's not needed nor used. This package manages it itself.
I removed the Package Control's LSP-typescript and install it the manual way from this repo, now works like a charm! Thank you for help!
Version v1.3.1 with the fix is now on package control.
Hello there, I open a ts file in my project, type some random words there to get some syntax errors but I don't see any diagnostics showing up to notify me about that. It was working fine when I first installed it days ago through package control:
This is how it looks now (auto-completion still works):
I have tried to re-install several times but no difference, hope I can have some help! Thank you, and here is the trouble-shooting:
Troubleshooting: LSP-typescript
Version
Server Test Run
Server Configuration
Active view
Project / Workspace
LSP configuration