Make VS Code use forked Hackatime extension#11
Conversation
Greptile SummaryThis PR switches the VS Code extension installed by the Hackatime setup tool from the upstream WakaTime extension (
Confidence Score: 4/5Safe to merge — the change is a straightforward swap of extension IDs with no logic changes, and the target extension exists on the VS Code marketplace. Both changed files correctly target hackatime.hackatime-time-tracker, which is a published marketplace extension. The only gap is that install.ps1 leaves the extension ID as a bare string while vscode.rs introduced a constant — a minor consistency issue that won't cause runtime failures. No files require special attention; both changes are small and low-risk. Important Files Changed
Sequence DiagramsequenceDiagram
participant User
participant Installer as install.ps1 / vscode.rs
participant VSCLI as VS Code CLI (code)
participant Marketplace as VS Code Marketplace
User->>Installer: Run setup
Installer->>VSCLI: --install-extension hackatime.hackatime-time-tracker
VSCLI->>Marketplace: Fetch extension
Marketplace-->>VSCLI: Extension package
VSCLI-->>Installer: Exit code 0
Installer-->>User: "Hackatime extension installed"
Prompt To Fix All With AIFix the following 1 code review issue. Work through them one at a time, proposing concise fixes.
---
### Issue 1 of 1
install.ps1:151
**Extension ID hardcoded inline in PowerShell, constant in Rust**
The Rust file centralized the extension ID as `EXTENSION_ID` constant, but `install.ps1` still has the string `"hackatime.hackatime-time-tracker"` inlined. If the extension ID ever changes, `install.ps1` and `vscode.rs` would need to be updated independently, risking drift. Consider extracting a variable (e.g., `$HackatimeExtensionId = "hackatime.hackatime-time-tracker"`) near the top of the VS Code install block for symmetry and maintainability.
Reviews (1): Last reviewed commit: "Make VS Code use forked Hackatime extens..." | Re-trigger Greptile |
hackclub/hackatime#1385