Closed bastiandoetsch closed 11 months ago
We are seeing the same issue in Cloud Code extension as well.
@mjbvz Any chance you can have a look at it?
Sorry to ping again about it, but this is rather a bad UX for users - any chance to have a look at it, @mjbvz?
similar to https://github.com/microsoft/vscode/issues/196938
I wasn't able to repro then in flutter, but taking a look at it again
Thanks, let me know if you need more information or help for reproducing. We have been able to reproduce reliably with several people and our Snyk extension.
Hey @justschen , were you able to find a way to fix the VSCode behaviour or how we from our side can avoid that?
Looking into this atm! @bastiandoetsch I'm unable to recreate in the Synk extension - is there a specific command that the extension contributes that causes this?
Thanks for investigating! It is happening with all actions provided by the language server. "Local" code actions that directly interface with VSCode don't show this behavior. The command json I pasted in the description is one of the examples (for opening a browser window).
If you wanna see it / debug it, I'm open to a video call.
Here's a screen recording displaying the issue:
https://github.com/microsoft/vscode/assets/20150761/fe3c9c93-23c5-4fa1-83d9-bb189b4bd22b
Using the Snyk extension, the following steps would be necessary to reproduce:
@justschen have you been able to recreate the issue now?
yes - deferring to december!
I'm a bit sad that it's deferred, but I'm happy that it's at last reproducible :).
this is fixed in the latest insiders! please try it out, and if it is unresolved, feel free to open a new issue
Thanks for fixing! Works like a charm!
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
Quickfixes...
menu, the code action command is automatically executed on mouse-over/selection.This is happening with current vscode versions, but not with 1.80.2 released in June, both using the same Snyk extension version. Therefore we think that a change in VSCode or one of its language server / language client related libraries is triggering this unexpected behaviour.