use different data model to prep ExtHostConfiguration for #inspect knowledge

This commit is contained in:
Johannes Rieken
2016-11-04 18:25:22 +01:00
parent 2b5b2bcd47
commit 697c06f216
7 changed files with 123 additions and 36 deletions

View File

@@ -7,7 +7,7 @@
import { TPromise } from 'vs/base/common/winjs.base';
import { IDisposable, dispose } from 'vs/base/common/lifecycle';
import { IThreadService } from 'vs/workbench/services/thread/common/threadService';
import { IWorkspaceConfigurationService } from 'vs/workbench/services/configuration/common/configuration';
import { IWorkspaceConfigurationService, getWorkspaceConfigurationTree } from 'vs/workbench/services/configuration/common/configuration';
import { IConfigurationEditingService, ConfigurationTarget } from 'vs/workbench/services/configuration/common/configurationEditing';
import { MainThreadConfigurationShape, ExtHostContext } from './extHost.protocol';
@@ -24,7 +24,11 @@ export class MainThreadConfiguration extends MainThreadConfigurationShape {
super();
this._configurationEditingService = configurationEditingService;
const proxy = threadService.get(ExtHostContext.ExtHostConfiguration);
this._toDispose = configurationService.onDidUpdateConfiguration(event => proxy.$acceptConfigurationChanged(event.config));
this._toDispose = configurationService.onDidUpdateConfiguration(() => {
const tree = getWorkspaceConfigurationTree(configurationService);
proxy.$acceptConfigurationChanged(tree);
});
}
public dispose(): void {