The "Linux JSON policies" section in docs/enterprise/policies.md correctly states the format is JSON and the file path is /etc/vscode/policy.json, but the Step 2 examples use macOS plist XML syntax (<key>, <string>, <true/>).
This causes parse failures because VS Code's FilePolicyService uses JSON.parse() to read the file.
Current (incorrect):
<key>AllowedExtensions</key>
<string>{"microsoft": true, "github": true}</string>
<key>EnableTelemetry</key>
<false/>Expected (correct JSON):
{
"AllowedExtensions": {"microsoft": true, "github": true},
"UpdateMode": "start",
"EnableFeedback": true,
"EnableTelemetry": false
}Source confirmation: FilePolicyService uses JSON.parse, and the build fixture is plain JSON.
The "Linux JSON policies" section in
docs/enterprise/policies.mdcorrectly states the format is JSON and the file path is/etc/vscode/policy.json, but the Step 2 examples use macOS plist XML syntax (<key>,<string>,<true/>).This causes parse failures because VS Code's
FilePolicyServiceusesJSON.parse()to read the file.Current (incorrect):
Expected (correct JSON):
{ "AllowedExtensions": {"microsoft": true, "github": true}, "UpdateMode": "start", "EnableFeedback": true, "EnableTelemetry": false }Source confirmation:
FilePolicyServiceusesJSON.parse, and the build fixture is plain JSON.