LSP completion breaks after first error in flow about asyncomplete-lsp.vim HOT 8 CLOSED

Please try asyncomplete v2 branch.

from asyncomplete-lsp.vim.

I don't get any LSP completions in v2 branch, in flow or typescript.

from asyncomplete-lsp.vim.

Also observed that in the master asyncomplete branch, the original error I reported does not happen with TypeScript (LSP completion works always). So it's flow LSP specific. I'm going to try to figure out what could have changed to cause this, but flow LSP completion is now way more fragile than it was a few days ago for me.

from asyncomplete-lsp.vim.

Closing since it is a bug on server.

from asyncomplete-lsp.vim.

Server as in the Flow package or the vim-lsp plugin? I can recreate the issue where you want and provide more extensive info...

from asyncomplete-lsp.vim.

Just downgraded to flow-bin 0.93 from 0.94, confirmed LSP completion works properly now. Do you have any info I can use to file an issue in the flow-bin repo? I don't know how to technically describe the issue, or if it's even an issue at all...

from asyncomplete-lsp.vim.

vimlsp and asyncomplete logs should be good enough. Feel free to ping me in their issue if you need help from my side.

from asyncomplete-lsp.vim.

Created flow/flow-bin#151
See facebook/flow#7545 instead

from asyncomplete-lsp.vim.