Microsoft/vscode
1
0
Fork 0
mirror of https://github.com/microsoft/vscode.git synced 2026-05-08 09:08:48 +01:00
Code Issues Packages Projects Releases Wiki Activity

Add "current window" command to testresolver.

Browse Source 
Seems like this is necessary to use the testresolver with normal extension debugging
This commit is contained in:
Rob Lourens
2021-12-10 11:36:46 -08:00
parent b3b82c0540
commit ad57fde11d
2 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
extensions/vscode-test-resolver/package.json
+6
View File
@@ -23,6 +23,7 @@
"activationEvents": [
"onResolveRemoteAuthority:test",
"onCommand:vscode-testresolver.newWindow",
"onCommand:vscode-testresolver.currentWindow",
"onCommand:vscode-testresolver.newWindowWithError",
"onCommand:vscode-testresolver.showLog",
"onCommand:vscode-testresolver.openTunnel",
@@ -59,6 +60,11 @@
"category": "Remote-TestResolver",
"command": "vscode-testresolver.newWindow"
},
{
"title": "Connect to TestResolver in Current Window",
"category": "Remote-TestResolver",
"command": "vscode-testresolver.currentWindow"
},
{
"title": "Show TestResolver Log",
"category": "Remote-TestResolver",
extensions/vscode-test-resolver/src/extension.ts
+3
View File
@@ -263,6 +263,9 @@ export function activate(context: vscode.ExtensionContext) {
context.subscriptions.push(vscode.commands.registerCommand('vscode-testresolver.newWindow', () => {
return vscode.commands.executeCommand('vscode.newWindow', { remoteAuthority: 'test+test' });
}));
context.subscriptions.push(vscode.commands.registerCommand('vscode-testresolver.currentWindow', () => {
return vscode.commands.executeCommand('vscode.newWindow', { remoteAuthority: 'test+test', reuseWindow: true });
}));
context.subscriptions.push(vscode.commands.registerCommand('vscode-testresolver.newWindowWithError', () => {
return vscode.commands.executeCommand('vscode.newWindow', { remoteAuthority: 'test+error' });
}));