-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Jump to definition doesn't work #38239
Comments
(Experimental duplicate detection) |
Yes, VSCode Bot, same issue but it needed more info |
Seemed like a duplicate of #18171 |
Out of curiosity, I've noticed in some other reports of this people mention TypeScript and I saw this get moved. What does TypeScript have to do with it? |
TypeScript powers the JavaScript experience in VS Code. |
Yeah, looks like a dupe of #38239. |
This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes. |
Version: 1.44.2
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T17:07:18.473Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.4.0
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
Here's my code:
When i try to go to the definition of
this.something()
I get an error saying "no definition found for something". This works in other editors I've used such as WebStorm/IntelliJ. It also worked at least a long time ago on Sublime when I used it. I understand that some things like globals might fail because you can't tell where it's coming from but this is a vanilla JS file where 100% of the definitions are defined in there. Even if a global was defined elsewhere this would be overriding it.I saw some others report this but those issues were closed about a year ago.
The text was updated successfully, but these errors were encountered: