-
Notifications
You must be signed in to change notification settings - Fork 1.2k
'Go to definition' not working #5199
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
Comments
This is #5132, I believe. |
'Go to Definition' not working after latest update of VSCode 1.33.1 Environment data Expected Behaviour: Actual Behaviour: But if you hover the implementation then it will show you the class with function name and all the parameters of the functions that are requested in definition of the function. It's also suggesting the function while implementing. So maybe there is some issue with only "Go to Definition". Things I've tried: @jakebailey @brettcannon If you guys have any suggestions please help. |
@kaushall please report it upstream at https://github.com/Microsoft/python-language-server. |
@brettcannon Can you please tell me how to do it, I'm bit new to github. |
@kaushall go to https://github.com/Microsoft/python-language-server/issues, click "New issue", and then fill in your details about your problem. |
Environment data
Expected behaviour
There is 'go to definition' in short cut menu, and press shortcut key defined in Visual Studio Code can lead to expected position.
Actual behaviour
No 'go to definition' in short cut menu, and press shortcut key defined in Visual Studio Code leads to nothing happens.



Steps to reproduce:
None
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Only startup logs:
Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)None, no output caused by operation.
The following are startup logs.
The text was updated successfully, but these errors were encountered: