Do not use noResolve with the LS

This commit is contained in:
Mohamed Hegazy
2014-07-19 11:30:10 -07:00
parent 9395eeaedb
commit 05eeba5bc9

View File

@@ -317,7 +317,15 @@ module TypeScript.Services {
throw Error("LanguageServiceShimHostAdapter.getCompilationSettings: empty compilationSettings");
return null;
}
return compilationSettingsToCompilerOptions(<ts.CompilerOptions>JSON.parse(<any>settingsJson));
var options = compilationSettingsToCompilerOptions(<ts.CompilerOptions>JSON.parse(<any>settingsJson));
/// TODO: this should be pushed into VS.
/// We can not ask the LS instance to resolve, as this will lead to asking the host about files it does not know about,
/// something it is not desinged to handle. for now make sure we never get a noresolve=true.
/// This value should not matter, as the host runs resolution logic independentlly
options.noResolve = true;
return options;
}
public getScriptFileNames(): string[] {