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

Intellisense for class methods is not working #28258

Closed
ebeloded opened this issue Jun 8, 2017 · 1 comment
Closed

Intellisense for class methods is not working #28258

ebeloded opened this issue Jun 8, 2017 · 1 comment
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) javascript JavaScript support issues typescript Typescript support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone

Comments

@ebeloded
Copy link

ebeloded commented Jun 8, 2017

When I create a class by extending another class or implementing an interface, the editor doesn't offer any helpful suggestions.

Typescript Service can show an error when abstract methods are not implemented, or if method signature is incorrect, but there is no help from the editor when I'm in the process of implementing the class.

An obvious example of this is implementing React Components. I expect that when I trigger suggest within the class implementation, I would see all of ComponentLifecycle methods with their signatures. However, when I invoke the suggest widget, it shows a host of things in there, none of which are helpful, and none of those I need are actually present.

screen shot 2017-06-09 at 05 01 56

Is this a bug or am I doing something wrong? I tried it with the new TypeScript-React-Starter project, but the behavior was the same.

  • VSCode Version: 1.12.2
  • OS Version: MacOS Sierra
@mjbvz mjbvz self-assigned this Jun 9, 2017
@mjbvz mjbvz added this to the June 2017 milestone Jun 9, 2017
@mjbvz mjbvz added *duplicate Issue identified as a duplicate of another issue(s) upstream Issue identified as 'upstream' component related (exists outside of VS Code) labels Jun 9, 2017
@mjbvz
Copy link
Collaborator

mjbvz commented Jun 9, 2017

I believe this is a duplicate of microsoft/TypeScript#7158

This is fixed in the latest TypeScript 2.4 insiders which we will pick up for VSCode 1.14:

screen shot 2017-06-09 at 12 51 00 pm

TS 2.4 should be in the VSCode insiders builds sometime next week

@mjbvz mjbvz closed this as completed Jun 9, 2017
@mjbvz mjbvz added javascript JavaScript support issues typescript Typescript support issues labels Jun 9, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) javascript JavaScript support issues typescript Typescript support issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

2 participants