Investigate Delayed Go-to-Definition Behavior in Editors
See original GitHub issueToday go-to-definition across files takes a minute in large projects when a file isn’t currently opened in an editor.
// a.ts
import "./b.js" // <- jump to definition on this path
// b.ts
export function foo() {
}
It’s not clear why this is the case when the language service is fully initialized and program loading has occured - the file path is already known (even when declaration maps are enabled). So it seems like the editor is taking a bit longer than it needs, or go-to-definition is being blocked by some other operation (which should potentially be considered lower-priority).
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Lack of Go to Definition in TypeScript - Visual Studio Feedback
This issue is currently being investigated. Our team will get back to you if either more information is needed, a workaround is available,...
Read more >Script Inspector 3 - World's Fastest IDE for Unity | Page 22 - Unity ...
I'm on a Mac, which has very standard behaviors for text editing that all good Mac apps (and most bad ones) follow. This...
Read more >Advice on improving Resharper 5.0 performance with VS2010 ...
It works without any delay for me so may go as a replacement workaround until ... goto definition, open unit test results etc....
Read more >Code of Conduct - Council of Science Editors
Upon receipt of a report of harassment or other unacceptable behavior, the incident will be investigated by the CSE President, President-Elect, and Executive ......
Read more >What Is Delayed Gratification? 5 Examples & Definition
The ability to exert “willpower” and delay the attainment of pleasure reveals certain types of inhibitory behavior. Here are a few ways someone...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@DanielRosenwasser Can you also test this in the latest VS Code insiders build to confirm this is still happening. I checked in a fix the hover issue @amcasey mentioned last week but am not sure if it would also fix this
I’m not sure this is tracking anything specific.