Can't enable or disable extension per workspace

[br3ndonland]

Extension Version

v2.29.0

VS Code Version

Version: 1.84.2
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:52:57.054Z
Electron: 25.9.2
ElectronBuildId: 24603566
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 23.0.0

Operating System

macOS Sonoma 14.0

Terraform Version

Terraform v1.5.7 on darwin_arm64

Steps to Reproduce

1. Navigate to extensions
2. Click the gear
3. View "Enable (Workspace)" or "Disable (Workspace)" in the popup menu

Expected Behavior

As of 2.28.2 (2023-10-16), it was possible to enable or disable the extension per workspace in VSCode.

Actual Behavior

As of 2.29.0 (2023-11-08), the extension cannot be enabled or disabled per workspace in VSCode.

This change does not appear to be mentioned in the release notes for 2.29.0.

Terraform Configuration

No response

Project Structure

No response

Gist

No response

Anything Else?

No response

Workarounds

Downgrade to extension v2.28.2

References

• https://code.visualstudio.com/docs/editor/extension-marketplace#_manage-extensions

Help Wanted

• I'm interested in contributing a fix myself

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[jpogran]

Hey @br3ndonland thanks for bringing this to our attention. This was not intended and I don't immediately know what we did yet that caused it to not be able to be disabled/enabled per workspace, but I'm going to try and figure out.

[neodon]

Thanks for looking into this @jpogran. Is there any update? I still can't enable the extension per-workspace, even with the pre-release version. It's really obnoxious.

[jpogran]

Apologies on the delayed reply, I was not able to update the ticket before the recent holidays. I opened microsoft/vscode-discussions#930 to ask why this behavior occurs. In short, because we advertise an authentication provider, we cannot be enabled or disabled per workspace. I'm not particularly happy about the reasoning or lack of documentation/warning about this, but it's outside of my ability to control and I have to work with what I've got.

Now that the holidays are over, this is back on my plate and I'm going to see what I can do to resolve this going forward. Unfortunately I still do not have a workaround at this time because of the way VS Code works.

[br3ndonland]

Thanks for the update @jpogran. I totally understand that some aspects of the VSCode Extensions API are outside your control, and appreciate your efforts with the upstream discussion in microsoft/vscode-discussions#930. If you figure out a solution and need some help testing development builds of the extension, I'm happy to help.

[jpogran]

Hi @br3ndonland, I just published a pre-release version of the extension with a potential fix. If you validate that it works for you, I'll merge it to main and publish a stable version soon.

[paul-at-cybr]

Works for me!

[panfiva]

@jpogran , fix worked for me as well

FYI: It seems that you version that you used to publish the fix (v2.29.2024011610) is less than the latest pre-release version (v2.29.2024011611):

[br3ndonland]

v2.29.2024011610 looks good, thanks @jpogran!

[tuananhlai]

The fix works for me! But I had to manually select the version v2.29.2024011610 as suggested by @panfiva.

[jpogran]

Thanks all for the feedback. We've merged this and released it in the latest stable: 2.29.3. @br3ndonland let me know if things don't work for you in stable.

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.