DesignLiquido / DesignLiquido/vscode
Três activationEvents apontam para comandos inexistentes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 172
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
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).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open package.json and inspect the activationEvents entries for runEditorContents, debugEditorContents, and getProgramName, checking them against contributes.commands and the extension code. Done means the three orphaned activation events are removed unless the related editor-execution issue establishes that they are required; verify the resulting package configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 84/100