Executing workbench.extensions.installExtension command with an invalid extension ID\Path swallows all exceptions #88713
Labels
bug
Issue identified by VS Code Team member as probable bug
extensions
Issues concerning extensions
verified
Verification succeeded
Milestone
We have a private extension that cannot be placed in the private gallery and we have our own update mechanism for our extension.
Previously it was re-launching VSCode (new process) to install\update the extension but it was pointed out to us that executing the ''workbench.extensions.installExtension' command also works. (The ms-vscode.cpptools extension does this already). However, while ensuring that this technique would work for our extension, I discovered that exceptions from the command implementations in src\vs\workbench\contrib\extensions\browser\extensions.contribution.ts where being "logged" but not "re-thrown" to the command executor.
We would like to leverage this command (instead of having to re-spawn VSCode) but we also have a very strong desire to know when things fail, so we haven't converted our code yet.
Steps to Reproduce:
Does this issue occur when all extensions are disabled?: Yes
Possible fix is to pass in an optional boolean parameter to re-throw the error if the users desires:
I'll issue a pull request for this fix and we can go from there.
The text was updated successfully, but these errors were encountered: