-
-
Notifications
You must be signed in to change notification settings - Fork 950
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ALE diagnostic signs don't appear #805
Comments
@chemzqm all works as expected on that linked repo? |
Reproduced, but it's ale's issue, coc send the diagnostics to ale as expected and doesn't display them. |
I found the bit of code where coc calls into ALE coc.nvim/src/diagnostic/manager.ts Line 513 in 536565f
Then I added debug output to And here is what it prints when vim starts: The last message call is an empty array which, according to that helpful comment right above the |
It's because there're two tsserver collection for typescript and javascript. |
Thank you - fixed! |
Result from CocInfo
CocConfig:
Describe the bug
ALE diagnostic signs don't appear.
Note, that I disabled
tsserver
ALE linter - because I am execting coc to do that. If thattsserver
is not disabled, then I can see diagnostic signs appear for a brief second and then disappear. But I don't want ALE to runtsserver
anyway.Reproduce the bug
Clone this repo https://github.com/artemave/coc-ale-test and run:
vim -u mini.vim test.ts
Screenshots (optional)
eslint error appears, but not the typescript one:
coc is aware of typescript errors:
The text was updated successfully, but these errors were encountered: