From 090baa56bf6072124742f07e89ec6bc001acaecb Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 31 Dec 2025 09:03:40 +0000 Subject: [PATCH 1/2] Initial plan From cfa228cea8ec6822613590d3bfbb0b68324341bb Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 31 Dec 2025 09:06:43 +0000 Subject: [PATCH 2/2] Fix hover window "Add to Watch" parameter order bug Fixed the bug where adding a variable to watch from hover window would incorrectly use "hover" as the variable name instead of the actual expression name. The issue was in run_hover() passing parameters in wrong order to variables.createRef(). Changed: variables.createRef(res, "hover") To: variables.createRef(res, expression, "hover") This now matches the correct implementation used in run_watch(). Co-authored-by: sumneko <5213431+sumneko@users.noreply.github.com> --- extension/script/backend/worker/evaluate.lua | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extension/script/backend/worker/evaluate.lua b/extension/script/backend/worker/evaluate.lua index 433178d2..21401b54 100644 --- a/extension/script/backend/worker/evaluate.lua +++ b/extension/script/backend/worker/evaluate.lua @@ -39,7 +39,7 @@ local function run_hover(frameId, expression) if not ok then return false, res end - local var = variables.createRef(res, "hover") + local var = variables.createRef(res, expression, "hover") var.result = var.value var.value = nil return true, var