fleet/ee/maintained-apps/inputs/homebrew/visual-studio-code.json

{
  "name": "Microsoft Visual Studio Code",
  "slug": "visual-studio-code/darwin",
  "unique_identifier": "com.microsoft.VSCode",
  "token": "visual-studio-code",
  "installer_format": "zip",
  "default_categories": ["Developer tools"]
}
Add missing VSCode FMA input/output (#27178) 2025-03-17 13:18:49 +00:00			`{`
			`"name": "Microsoft Visual Studio Code",`
			`"slug": "visual-studio-code/darwin",`
			`"unique_identifier": "com.microsoft.VSCode",`
			`"token": "visual-studio-code",`
software categories: backend (#28479) > For #28138 # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [x] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [x] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). - [x] Added/updated automated tests - [x] A detailed QA plan exists on the associated ticket (if it isn't there, work with the product group's QA engineer to add it) - [x] Manual QA for all new/changed functionality --------- Co-authored-by: Ian Littman <iansltx@gmail.com> 2025-05-02 15:41:26 +00:00			`"installer_format": "zip",`
			`"default_categories": ["Developer tools"]`
			`}`