Flow-for-vscode: Autocomplete/IntelliSense works only under very specific circumstances

Created on 4 Apr 2018 · 5Comments · Source: flowtype/flow-for-vscode

flow-autocomplete-issue

Maybe I'm doing something completely wrong but I've been trying to get flow working nicely in VSCode for several hours. I've concluded that IntelliSense with flow has some real issues and recorded this gif showing two ways I believe it's broken:

Chaining causes IntelliSense to stop working.
Trying to use it preceding an anonymous function without a semicolon somewhere between causes IntelliSense to stop working.

These issues may be related. Needless to say, it's making Flow pretty difficult to work with.

FWIW, Identical behaviour in Atom.

flow 0.69.0
flow-for-vscode 0.8.0

Source

lukebarton

Most helpful comment

Same, I can't get flow to give me any intellisense at all. I've disabled vscode's inbuild typescript plugin.

kumarharsh on 5 Apr 2018

👍14

All 5 comments

Same, I can't get flow to give me any intellisense at all. I've disabled vscode's inbuild typescript plugin.

kumarharsh on 5 Apr 2018

👍14

Did anyone got both Flow and IntelliSense working?

princiya on 27 Jul 2018

Alright I guess this is still an issue.

VSCode intellsense has evolved (nice thing).

But typing string will be suggested String.

So if you don't pay attention it will write String (from JS class since VSCode does not know about flow types). Really annoying.

Is there a way to feed VScode intellisense (I'm not used to create VSCode extension)?

MacKentoch on 15 Apr 2019

👍2

Well... yes, this plugin is supposed to provide intellisense (among other things). Maybe there's a chance your flow binary/this extension is not working correctly... Also, it'll probably not work if you're in Windows.

kumarharsh on 15 Apr 2019

@MacKentoch in the extension sidebar, type @builtin typescript and then click the settings cog to disable for your project or globally. After a reload it should look like this: