Type: Bug
For example, view the information on the built-in Git extension.
A command that doesn't appear on the Command Palette (because the extension's package.json explicitly qualifies its contribution with a "when": "false") displays commandPalette in the Menu Contexts column (e.g. git.api.getRepositories)
Conversely a command that does appear has no commandPalette entry (e.g. git.checkoutDetached)
The extension editor should handle that commands appear on the palette by default (no entry required in package.json) and that "when": "false" is the recommended way of hiding commands that shouldn't / can't be used from Command Palette.
VS Code version: Code - Insiders 1.94.0-insider (527e41f, 2024-09-20T05:03:57.400Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Type: Bug
For example, view the information on the built-in Git extension.
A command that doesn't appear on the Command Palette (because the extension's package.json explicitly qualifies its contribution with a
"when": "false") displayscommandPalettein the Menu Contexts column (e.g.git.api.getRepositories)Conversely a command that does appear has no
commandPaletteentry (e.g.git.checkoutDetached)The extension editor should handle that commands appear on the palette by default (no entry required in package.json) and that
"when": "false"is the recommended way of hiding commands that shouldn't / can't be used from Command Palette.VS Code version: Code - Insiders 1.94.0-insider (527e41f, 2024-09-20T05:03:57.400Z)
OS version: Windows_NT x64 10.0.22631
Modes: