-
Notifications
You must be signed in to change notification settings - Fork 28.9k
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
[Extension API] executeCommand 'editor.action.goToDeclaration' returns immediately #65809
Comments
It does but only when calling it with correct arguments. In this case the position is missing and will have gotten an error for that. |
We have a great developer community over on slack where extension authors help each other. This is a great place for you to ask questions and find support. Happy Coding! |
Do you have an example of how it should be called (ie. what are the correct arguments)? Don't see any docs or examples of a position being passed to |
Sorry, I had the wrong command in mind. Things should work the way you have written them. The editor must have a file open that supports go to declaration and it must not be an embedded editor, otherwise there are no restrictions. |
Yes, and yes. It probably helps if I shared the file of where I ran |
There is actually one level of promises that we don't await. I will push a fix |
Issue Type: Bug
I expected
executeCommand
to return once thegoToDeclaration
action has completed.Sample Code:
Console Output:
VS Code version: Code 1.30.1 (dea8705, 2018-12-18T18:12:07.165Z)
OS version: Windows_NT x64 10.0.17134
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
Extensions (5)
The text was updated successfully, but these errors were encountered: