mirror of
https://github.com/microsoft/TypeScript.git
synced 2026-05-19 10:41:56 -05:00
Do not use noResolve with the LS
This commit is contained in:
@@ -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[] {
|
||||
|
||||
Reference in New Issue
Block a user