Skip to content

docs(vscode-extension): stop the keybinding example from stealing the Command Palette #8856

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.

Sign up for GitHub

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

Merged
os-zhuang merged 1 commit into from
Sep 9, 2026
Merged

docs(vscode-extension): stop the keybinding example from stealing the Command Palette #8856

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion content/docs/utilities/vscode-extension.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -374,12 +374,21 @@ command by its name, and assign a chord. To write the binding by hand instead, o

```json
{
"key": "ctrl+shift+p",
"key": "ctrl+alt+shift+f19",
"command": "objectui.preview",
"when": "editorLangId == json"
}
```

The `key` above is a stand-in, not a proposal — a deliberately far-fetched chord
that nothing binds, there to show the shape of an entry. Pick your own, and pick one
you are not already using: an entry in your `keybindings.json` overrides VS Code's
default for that chord, and the `when` clause only narrows *where* your entry
applies (here, JSON editors) — it does not decide whether your entry wins. Binding
`ctrl+shift+p`, for instance, would take the Command Palette away from you in JSON
files, which is where your schemas are open and where this page keeps sending you
for these commands.

Every command the extension contributes, with the id to bind:

| Command | Command id |
Expand Down