Refs: #33248
Have the following extension.ts. Debug that extension, notice that the contributed configuration for type node does not get merged into the final result. The results coming from the real node adapter are overwriting it.
This might be coming from the fact that node is also resolving debug configurations or we are not properly merging on the vscode side.
Assigning first to @weinand and feel free to assign back to me
'use strict';
// The module 'vscode' contains the VS Code extensibility API
// Import the module and reference it with the alias vscode in your code below
import * as vscode from 'vscode';
// this method is called when your extension is activated
// your extension is activated the very first time the command is executed
export function activate(context: vscode.ExtensionContext) {
// Use the console to output diagnostic information (console.log) and errors (console.error)
// This line of code will only be executed once when your extension is activated
console.log('Congratulations, your extension "ts-extension" is now active!');
vscode.debug.registerDebugConfigurationProvider('node', {
provideDebugConfigurations: (folder: vscode.WorkspaceFolder | undefined, token) => {
return [{
type: 'isidor',
request: 'launch',
hello: 'tasty',
path: folder.uri.fsPath
}];
}
});
// The command has been defined in the package.json file
// Now provide the implementation of the command with registerCommand
// The commandId parameter must match the command field in package.json
let disposable = vscode.commands.registerCommand('extension.sayHello', () => {
// The code you place here will be executed every time your command is executed
// Display a message box to the user
vscode.window.showInformationMessage('Hello World!');
});
context.subscriptions.push(disposable);
}
Refs: #33248
Have the following
extension.ts. Debug that extension, notice that the contributed configuration for type node does not get merged into the final result. The results coming from the real node adapter are overwriting it.This might be coming from the fact that node is also resolving debug configurations or we are not properly merging on the vscode side.
Assigning first to @weinand and feel free to assign back to me