Skip to content
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

Strange intellisense prediction #26624

Closed
devinrhode2 opened this issue May 14, 2017 · 1 comment
Closed

Strange intellisense prediction #26624

devinrhode2 opened this issue May 14, 2017 · 1 comment
Assignees
Labels
*as-designed Described behavior is as designed javascript JavaScript support issues *question Issue represents a question, should be posted to StackOverflow (VS Code)

Comments

@devinrhode2
Copy link

Steps to Reproduce:
vscode-chromedot-bug

  • VSCode Version: Code 1.12.1 (f6868fc, 2017-05-04T21:18:32.269Z)
  • OS Version: Darwin x64 15.6.0
  • Extensions:
Extension Author Version
visual-studio-light-theme SimoneOlivieri 0.0.7
elm-format abadi199 0.1.0
vscode-color anseki 0.2.2
vscode-eslint dbaeumer 1.2.8
vscode-babel-coloring dzannotti 0.0.4
vsc-ember-cli felixrieseberg 0.3.1
Theme-Capo-Light gerane 0.0.3
ide-purescript nwolverson 0.4.3
language-purescript nwolverson 0.0.7
vscode-format ryannaddy 0.0.5
elm sbrink 0.8.3
react-beautify taichi 0.3.0
html-preview-vscode tht13 0.0.3

Don't think the filename would be relevant, but it was "7-considerActivating.js".

@mjbvz mjbvz added *as-designed Described behavior is as designed javascript JavaScript support issues *question Issue represents a question, should be posted to StackOverflow (VS Code) labels May 15, 2017
@mjbvz
Copy link
Collaborator

mjbvz commented May 15, 2017

Yes, our intellisense does not know about any chrome global which is why you don't see it recommended. If the visible suggestions are not helpful, you can always cancel out of them using escape

To get proper suggestions for chrome, try installing @types/chrome in you project. The easiest way is to create a jsconfig.json at the root of your project with the content:

{
    "typeAcquisition": {
        "include": [
            "chrome"
        ]
    }
}

This should let VSCode know about the chrome global in javascript files

We also should not be suggesting the RTC... type at all in JS files. This is tracked by: microsoft/TypeScript#15750

Closing as designed

@mjbvz mjbvz closed this as completed May 15, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed javascript JavaScript support issues *question Issue represents a question, should be posted to StackOverflow (VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants