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

Cntrl click on an object reference in a TS file, takes ~17 seconds to open the file #35603

Closed
jrmcdona opened this issue Oct 5, 2017 · 3 comments
Assignees
Labels
info-needed Issue requires more information from poster typescript Typescript support issues

Comments

@jrmcdona
Copy link

jrmcdona commented Oct 5, 2017

  • VSCode Version: 1.16.1 64 bit (although this was happening on 32 bit)
  • OS Version:

OS Name: Windows
OS Version: 10.0.15063
OS Platform: Windows

Steps to Reproduce:

  1. When I click on a reference to an object, it takes almost 20 seconds for the file to open up
    For example:
    I have this contructor:
constructor(private seasonsService: SeasonsService) {
  }

When I cntl click on SeasonsService, it will take 17 seconds to open up seasons.service.ts file.

This happens on more than one project. It used to work fine and not sure what would be causing this.

It may be worth noting here that Intelliense in C# stopped working too but TypeScript typed objects still get intellisense. I logged an issue with the C# extension but that seems much different than the issue I stated here.

Reproduces without extensions: Yes

@vscodebot vscodebot bot assigned mjbvz Oct 5, 2017
@vscodebot vscodebot bot added the typescript Typescript support issues label Oct 5, 2017
@mjbvz mjbvz added the info-needed Issue requires more information from poster label Oct 11, 2017
@mjbvz
Copy link
Collaborator

mjbvz commented Oct 11, 2017

Possible related to microsoft/TypeScript#16329

  1. Do you have a tsconfig.json and are both files part of this project? You can check this by running TypeScript: go to configuration in vscode for each file. This command should open up the tsconfig

  2. Also can you please try updating to VSCode 1.17 and installing the latest TypeScript 2.6 dev build in your workspace by running npm install typescript@next and following these instructions to see if fixes the issue

@vscodebot
Copy link

vscodebot bot commented Oct 18, 2017

This issue has been closed automatically because it needs more information and has not had recent activity. Please refer to our guidelines for filing issues. Thank you for your contributions.

@vscodebot vscodebot bot closed this as completed Oct 18, 2017
@jrmcdona
Copy link
Author

The answer to #1 was yes to both.

In the end it seemed to resolve itself. Will keep an eye on it for bad behavior/

Thanks

@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 2, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
info-needed Issue requires more information from poster typescript Typescript support issues
Projects
None yet
Development

No branches or pull requests

2 participants