Extension broken with the latest VS Code update (1.57.0-insider) about vscode-which-key HOT 10 CLOSED

Thanks Steven. My life is back on track again.

from vscode-which-key.

I didn't do the version gating correctly in the last version and I thought I would have released v0.9.0 by now which includes the fix.

Issued v0.8.6 that includes the proper version gating. Sorry about that.

from vscode-which-key.

Sorry for the regression. Released v0.9.1 that should fix it.

Btw, I also edited your post to have an expandable toggle for your config reduce the page length of the post.

from vscode-which-key.

VScode changed how they handle input change event @ microsoft/vscode#122939. I am looking into fixing it.

from vscode-which-key.

Fixed in 3212562 and released v0.8.5

from vscode-which-key.

Thanks Steven 🙏

from vscode-which-key.

The issue seems to come back again with 1.58-insider. Haven't tested it on Mac yet, but just discovered it when I updated just now on Windows.

from vscode-which-key.

Not sure what I updated this time, but now with v0.9.0 in Windows, no menu items show in the dropdown, only an input box. pressing any key would also just give me an undefined error in the status bar...

from vscode-which-key.

@pingshunhuangalex I tested the v0.9.0 n on 1.58-insider, it seems to fine. Can you share your configs?

from vscode-which-key.

Thanks for the reply @stevenguh It looks like triggering the extension directly from VS Code menu works fine, but triggering it using the shortcut (backslash) set by myself doesn't. Configs below:

"vim.normalModeKeyBindingsNonRecursive": [
    {
      "before": ["\\"],
      "commands": ["whichkey.show"]
    },
],
"vim.visualModeKeyBindingsNonRecursive": [
    {
      "before": ["\\"],
      "commands": ["whichkey.show"]
    },
],

...

"whichkey.bindings": [
    {
      "key": "\\",
      "name": "Commands...",
      "type": "command",
      "command": "workbench.action.showCommands"
    },
    ...
],

from vscode-which-key.