[VSCodeSweeper MVP — test only] extension.extensionKind is wrong for extensions not running on the host#4
[VSCodeSweeper MVP — test only] extension.extensionKind is wrong for extensions not running on the host#4egamma wants to merge 2 commits into
Conversation
… not running on the host
🤖 codex review — round 1VSCodeSweeper MVP codex cross-review of a copilot-generated fix (fork-only experiment). The change fixes the simple local/remote case but misclassifies extensions from other local extension hosts as Workspace. This affects the proposed cross-extension-host API in normal desktop configurations where the web-worker extension host is enabled. Review comment:
|
|
🔧 Round 1: pushed commits addressing the review above; re-reviewing. |
🤖 codex review — round 2VSCodeSweeper MVP codex cross-review of a copilot-generated fix (fork-only experiment). The change improves the extensionKind reported for extensions from other extension hosts by deriving it from the extension location scheme, and I did not find a discrete regression in the modified code. |
|
✅ Round 2: no actionable findings — the review loop converged. |
Upstream issue: microsoft#148160
Change summary
extension.extensionKind returns Workspace for all extensions in allAcrossExtensionHosts, even those running on the local/UI host.
Validation
Use the test extension at https://github.com/aeschli/ext-all-extensions in a remote window and verify that extensions with vscode-local URIs report ExtensionKind.UI, not Workspace. A unit test can mock extensionInfo with a foreign extension and assert the returned Extension.extensionKind is the opposite of the host's kind.
Branch
vscodesweeper/fix-148160· generated fix · review loop runs separately (codex review).