chore: use vitest as the controller name

vitest-dev · Feb 19, 2024 · 50b2169 · 50b2169
1 parent 867b63b
commit 50b2169
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/src/config.ts b/src/config.ts
@@ -5,7 +5,8 @@ import { log } from './log'
 import { isDefinitelyVitestEnv, mayBeVitestEnv } from './pure/isVitestEnv'
 import { getVitestCommand, getVitestVersion, isNodeAvailable } from './pure/utils'
 
-export const extensionId = 'zxch3n.vitest-explorer'
+export const extensionId = 'vitest.explorer'
+export const testControllerId = 'vitest'
 
 export function getConfigValue<T>(
   rootConfig: WorkspaceConfiguration,

diff --git a/src/extension.ts b/src/extension.ts
@@ -8,7 +8,6 @@ import { TestFile, WEAKMAP_TEST_DATA } from './TestData'
 import { Command } from './command'
 import {
   detectVitestEnvironmentFolders,
-  extensionId,
   getConfig,
   getVitestWorkspaceConfigs,
   vitestEnvironmentFolders,
@@ -34,7 +33,7 @@ export async function activate(context: vscode.ExtensionContext) {
     return
   }
 
-  const ctrl = vscode.tests.createTestController(`${extensionId}`, 'Vitest')
+  const ctrl = vscode.tests.createTestController('vitest', 'Vitest')
 
   const workspaceConfigs = await getVitestWorkspaceConfigs()
   // enable run/debug/watch tests only if vitest version >= 0.12.0