Extensions Recommendations : Can't undo "Don't Show Again for this Repository"

[kevinmarrec]

Environment

• VS Code Version: 1.96.4
• OS Version: Windows 11

Does this issue occur when all extensions are disabled ?
Not applicable

Description

When a workspace provide a .vscode/extensions.json file to provide extensions recommendations, a notification is displayed and there's an option to never show it again for this workspace.

If clicked, it saves the action as a Workspace state entry which can't be undone from VSCode UI or configuration files.

Workspace states are usually found there: %vscodeInstallFolder%/User/workspaceStorage/%id/state.vscdb
These states have .vscdb extensions which seem to be backed by SQLite.

The only way to undo it seems to either re-install VSCode or manually delete workspace states but I don't consider it as viable solution for the following reasons : not user friendly, not documented and therefore especially not error proof.

Here's the storage key that can't be unset forever :
https://github.com/microsoft/vscode/blob/main/src/vs/workbench/contrib/extensions/browser/extensionRecommendationNotificationService.ts#L44

Solution

Provides a VSCode command (F1) that would reset this action. (Ex: "Workspace: Reset extensions recommendations notifications")

Two possible implementations :

• Toggling the boolean from true to false in the workspace state
• Remove the key from workspace state

[gjsjohnmurray]

See #24815

[kevinmarrec]

Thank you for the link @gjsjohnmurray

Well, unfortunately the issue state is:

• Opened 8 years old (Q2 2017)
• Locked in early 2021 (Q1 2021)
• Ignored in January 2021 Iteration Plan (Iteration Plan for January 2021 #112419)
• Reopened mid 2021 (Q2 2021)

I don't know what we can do.

Based on my little dives into the VSCode codebase, I'm not sure it would be such a big deal to at least develop a part of the request (could be implementing it only for a single storage key first, then go generic).

[sandy081]

/duplicate

#24815

[vs-code-engineering]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

[kevinmarrec]

@sandy081 Are we stuck with conversation locked 2017 issue ?

It seems @meganrogge implemented once a solution (#114114) but it has been closed, not merged.

If at least someone with collaborator access could give a state update to the main github issue #24815 as it's locked.

Thanks 🙏

[sandy081]

Hi @kevinmarrec

Unfortunately #24815 is not in our near term Roadmap, hence it is not being attended. We will get back to this when it gets prioritised in our Roadmap. Unfortunately, I do not have any timeline. Sorry about that.

Thanks for understanding.

CC @bpasero