From 1835b4f06189560eb17a103b8db05e011a7cd799 Mon Sep 17 00:00:00 2001 From: David Sherret Date: Sun, 14 Apr 2024 20:07:04 -0400 Subject: fix(lsp): ensure project version is incremented when config changes (#23366) I'm running into a node resolution bug in the lsp only and while tracking it down I noticed this one. Fixed by moving the project version out of `Documents`. --- cli/tsc/99_main_compiler.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'cli/tsc/99_main_compiler.js') diff --git a/cli/tsc/99_main_compiler.js b/cli/tsc/99_main_compiler.js index 274fc1cca..be9962814 100644 --- a/cli/tsc/99_main_compiler.js +++ b/cli/tsc/99_main_compiler.js @@ -165,7 +165,7 @@ delete Object.prototype.__proto__; /** @type {ts.CompilerOptions | null} */ let tsConfigCache = null; - /** @type {string | null} */ + /** @type {number | null} */ let projectVersionCache = null; const ChangeKind = { @@ -1039,7 +1039,7 @@ delete Object.prototype.__proto__; case "$projectChanged": { /** @type {[string, number][]} */ const changedScripts = args[0]; - /** @type {string} */ + /** @type {number} */ const newProjectVersion = args[1]; /** @type {boolean} */ const configChanged = args[2]; -- cgit v1.2.3