Três activationEvents apontam para comandos inexistentes

[leonelsanchesdasilva]

Problema

Três activationEvents apontam para comandos inexistentes (runEditorContents, debugEditorContents, getProgramName), herança do modelo mock-debug do VSCode. Esses comandos não existem nem em contributes.commands nem no código.

Sugestão

Remover os três activationEvents órfãos de package.json, a menos que haja intenção de implementar de fato um modelo de execução baseado neles (ver issue sobre execução de projeto pelo editor).

---

Origem: Relatório de Produtividade — Extensão Design Líquido para VSCode v0.27.5 (achado B1, severidade baixa).

[kunaaaalcodes]

@leonelsanchesdasilva

This issue has already been resolved in commit f249146, which was merged as part of PR #124 (fixes #105).

During that change, the obsolete activationEvents inherited from the VS Code mock-debug sample were removed:

• onCommand:extension.designliquido.getProgramName
• onCommand:extension.designliquido.runEditorContents
• onCommand:extension.designliquido.debugEditorContents

These commands were never registered in contributes.commands nor implemented anywhere in the extension, so they were safe to remove.

The current activationEvents are now limited to the two debug events that are actually used:

"activationEvents": [
  "onDebugResolve:designliquido",
  "onDebugDynamicConfigurations:designliquido"
]