@JamieMagee thanks for this PR. So this gets rid of our own cgmanifest schema which makes sense.
Assigning to @aeschli for review for schema smarts
fyi @lszomoru

$schema is not the most elegant way. Note that $schema is not a standard, just a convenience invented by the JSON support in VS Code.

The easiest way would have been to change the schema association in '.vscode/settings' to use 'https://json.schemastore.org/component-detection-manifest.json'.

Alternative is to have a schema association in one of our built-in extensions. extension-editing would be a good place.

@aeschli I thought that $schema was part of the standard? It's documented here. Regardless, I can revert the changes and add the association in .vscode/settings.json for now.

If I were to make the change in extension-editing, where would I need to make it?

@JamieMagee That would be here: https://github.com/Microsoft/vscode/blob/main/extensions/extension-editing/package.json#L35

@aeschli I made the change you suggested in .vscode/settings.json. I'll send a followup PR for extension-editing at a later date.

Sneaking in September as this is a safe and simple change.

YOLO :)

@isidorn as second reviewer :-)