fix: make hatch.envInterpreter enablement a valid when-clause

[d-biehl]

Fixes #194.

Problem

hatch.envInterpreter was contributed with "enablement": false — a boolean. Per the contribution-points reference, a command's enablement is a when clause, i.e. a string context-key expression (the commandType schema in menusExtensionPoint.ts declares it as type: 'string').

VS Code passes the value straight to ContextKeyExpr.deserialize, whose scanner calls charCodeAt on it. A boolean has no charCodeAt, so it throws a TypeError that aborts the commands extension-point handler mid-iteration. Every extension whose commands are registered after Hatch then loses its command registration: those commands disappear from the Command Palette, and VS Code logs Menu item references a command ... which is not defined in the 'commands' section. for each of their menu items.

The effect is order-dependent and platform-independent (reproduced on Linux and Windows, on VS Code stable and Insiders).

Fix

Make enablement a valid when-clause expression by using the string "false" instead of the boolean:

"commands": [
  {
    "command": "hatch.envInterpreter",
    "title": "Hatch: Get an environment’s interpreter path",
    "enablement": "false"
  }
]

hatch.envInterpreter is only invoked programmatically via executeCommand (see src/extension.ts), so it never needs a UI affordance. enablement: "false":

• fixes the crash (a string deserializes fine),
• hides the command from the Command Palette (the palette filters out disabled commands), and
• disables it across all menus and keybindings — broader than a commandPalette when clause, which only covers the palette.

executeCommand bypasses enablement, so the command stays fully usable programmatically. biome check passes.

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

This PR migrates the hatch.envInterpreter command's palette-hiding configuration from the deprecated enablement: false property to the recommended menus.commandPalette with when: "false" clause.

Changes:

• Removes the enablement property from the command declaration.
• Adds a menus.commandPalette entry to hide the command from the command palette.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[flying-sheep]

Please use enablement instead: https://code.visualstudio.com/api/references/contribution-points#contributes.menus

Note that when clauses apply to menus and enablement clauses to commands. The enablement applies to all menus and even keybindings while the when only applies to a single menu.

That’s what we want.

[d-biehl]

Switched to "enablement": "false" (string) as suggested. 👍