Show Type Hierarchy breaks in vscode-insiders

[Eskibear]

Version: 1.69.0-insider (user setup)
Commit: f361c5b71d6676cfc6de97cdb1cc40b08bf7d994
Date: 2022-06-22T05:17:09.661Z
Electron: 18.3.4
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT x64 10.0.22000

Root cause is renaming of ref-viewlet's publisher. On our side, we can ask both old/new extension ids for compatibility, by PR #2517 . VS Code team will also take action to keep some backward compatibility. More details in see microsoft/vscode#152213 (comment)

[jdneo]

I saw the upstream name has been changed back to vscode.xxx. Is ms-vscode.xxx already released?

[CsCherrYY]

Is ms-vscode.xxx already released?

The extension name is always ms-vscode.xxx since it's available as an API, and we also use the ms-vscode.xxx to fetch the extension API.

Currently we should track microsoft/vscode#152834, the milestone is June so that there might be a solution before the new release of VS Code stable?

[Eskibear]

So far in all stable versions, it's ms-vscode.
In the coming June release (latest insiders), it's changed to vscode, and will stay as vscode for consistency.

On VS Code side, they will probably change implementation of getExtension so that it will return the instance even if you are using old publisher ms-vscode, for compatibility.

On our side, before that happen, to unblock the broken use case in insiders (and future releases), we should call getExtension using new publisher. To keep compatibility with current versions of vscode, fallback to getExtension with older publisher if the new one doesn't work.