What
Three command titles in packages/vscode/package.json#contributes.commands render poorly on the Feature Contributions tab of the extension's detail page (VS Code Extensions sidebar + the Marketplace listing). The Feature Contributions tab lists every declared command regardless of commandPalette when:false, so palette-hidden commands still surface here.
The three offenders
Internal command |
Current title |
Palette-hidden? |
codev.openBuilderTerminal |
Codev: Open Builder Terminal |
No |
codev.openBuilderById |
Codev: Open Builder Terminal |
Yes (when: "false") |
codev.openBuilderRow |
Codev: Open Builder Terminal (and expand row) |
Yes (when: "false") |
What users see
The Feature Contributions tab shows:
- "Codev: Open Builder Terminal" (×2 — visually identical lines, indistinguishable)
- "Codev: Open Builder Terminal (and expand row)" — reads like a debugger-style internal name
Result: confusing to anyone reading the extension's contribution list to figure out what it does.
Suggested fix
Distinct, user-meaningful title strings for the two internal commands, e.g.:
codev.openBuilderById → Codev: Open Builder Terminal (internal — by id) or similar (anything making clear it isn't the one to invoke from the palette). Alternatively, omit a title and only set category — though VS Code requires title, so we have to pick some string.codev.openBuilderRow → either drop the parenthetical or give it a description that doesn't read like dev notes — e.g. Codev: Open Builder Terminal and Expand Row.
Worth considering: since both internal commands are palette-hidden anyway, the cleanest fix may be a clearly-internal naming prefix (e.g. Codev (internal): …) so anyone reading the Feature Contributions tab can tell at a glance which entries are user-callable.
File to change
packages/vscode/package.json — contributes.commands[*] entries for codev.openBuilderTerminal, codev.openBuilderById, codev.openBuilderRow.
Acceptance
- No two visible commands in the Feature Contributions tab share the same title.
- No command title reads like a parenthetical debug note to a first-time reader.
Discovered while
Auditing the VS Code extension's auto-generated Feature Contributions tab during the README revision pass (see docs/vscode-readme-revision branch).
What
Three command titles in
packages/vscode/package.json#contributes.commandsrender poorly on the Feature Contributions tab of the extension's detail page (VS Code Extensions sidebar + the Marketplace listing). The Feature Contributions tab lists every declared command regardless ofcommandPalettewhen:false, so palette-hidden commands still surface here.The three offenders
commandtitlecodev.openBuilderTerminalCodev: Open Builder Terminalcodev.openBuilderByIdCodev: Open Builder Terminalwhen: "false")codev.openBuilderRowCodev: Open Builder Terminal (and expand row)when: "false")What users see
The Feature Contributions tab shows:
Result: confusing to anyone reading the extension's contribution list to figure out what it does.
Suggested fix
Distinct, user-meaningful
titlestrings for the two internal commands, e.g.:codev.openBuilderById→Codev: Open Builder Terminal (internal — by id)or similar (anything making clear it isn't the one to invoke from the palette). Alternatively, omit atitleand only setcategory— though VS Code requirestitle, so we have to pick some string.codev.openBuilderRow→ either drop the parenthetical or give it a description that doesn't read like dev notes — e.g.Codev: Open Builder Terminal and Expand Row.Worth considering: since both internal commands are palette-hidden anyway, the cleanest fix may be a clearly-internal naming prefix (e.g.
Codev (internal): …) so anyone reading the Feature Contributions tab can tell at a glance which entries are user-callable.File to change
packages/vscode/package.json—contributes.commands[*]entries forcodev.openBuilderTerminal,codev.openBuilderById,codev.openBuilderRow.Acceptance
Discovered while
Auditing the VS Code extension's auto-generated Feature Contributions tab during the README revision pass (see
docs/vscode-readme-revisionbranch).