-
Notifications
You must be signed in to change notification settings - Fork 36.9k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugconfigVS Code configuration, settingsVS Code configuration, settingsinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersverifiedVerification succeededVerification succeeded
Milestone
Description
Does this issue occur when all extensions are disabled?: Yes
- VS Code Version: 1.98.1
- OS Version: Windows/macOS
Some descriptions fetched in the policy generating script are incorrect.
Steps to Reproduce (in OSS):
- Run
cd build && npm run watch - From the root, run
node build/lib/policies(ornode build/lib/policies win32if this PR is merged) - Note that the files generated in
.build/policies/win32/<some-locale>for AllowedExtensions have a description of "No extensions are allowed".
That string is coming from here, and what should be selected is apparently this string - the more friendly:
"Specify a list of extensions that are allowed to use. This helps maintain a secure and consistent development environment by restricting the use of unauthorized extensions. For more information on how to configure this setting, please visit the Configure Allowed Extensions section."
From the local group policy editor
related to #148942
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugconfigVS Code configuration, settingsVS Code configuration, settingsinsiders-releasedPatch has been released in VS Code InsidersPatch has been released in VS Code InsidersverifiedVerification succeededVerification succeeded