-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
support new "selection" feature of debug completion items #90974
Comments
I do not think there will be time for this this milestone. PR to fix this is welcome |
I have pushed a change that when the Also fyi @connor4312 |
@isidorn I'll add code to Mock debug to exercise the completion request. |
@isidorn I've added two new completions items to Mock Debug: It seems that you are ignoring the selection if the attribute "selectionStart" is set but "selectionLength" is missing (as done in the "array[]" case). |
Oh, so that means just place the cursor. Got it. Yeah I can do the change. |
I have a change ready to go for this in js-debug as well once the next insiders is released |
@weinand pushed a change to cover that case and infer that |
@isidorn this works fine now, thanks! |
We've added support in the DAP for controlling the selection after a completion item has been inserted. See microsoft/debug-adapter-protocol#87.
Now VS Code needs to implement the client side of this feature.
Implementation hint: controlling the selection in VS Code seems to be only possible by using the snippet support. So it might be necessary to convert the result from the DAP completion request into a snippet that uses variables to specify the selection.
The text was updated successfully, but these errors were encountered: