Surface the vscode://schemas/color-theme schema to allow for programmatic use

[gesslar]

Either in the repository or from the Theme Color page, providing the schema will allow theme engine developers access to linting, information, in particular to CLI tools where they may not be in a VS Code environment, such as a CI/CD.

After creation of a theme, such tools would be able to validate against the schema, surfacing warnings and errors about the resulting JSON data, such as:

• invalid property names
• missing property names
• incorrect values; ex: some values need to have transparency
• etc

These are all visible within the UI when viewing and interacting with a theme's JSON, and is fantastic in that context, however, in a non-graphical context, developers need access to the schema to perform any number of validations to ensure correctitude and behavioural consistency.

[aeschli]

The vscode://schemas/color-theme scheme is dynamic and constructed at runtime: The number of colors varies based on the extensions installed and the default values of the colors depend on the current theme.

[vs-code-engineering]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[gesslar]

The vscode://schemas/color-theme scheme is dynamic and constructed at runtime: The number of colors varies based on the extensions installed and the default values of the colors depend on the current theme.

Thank you for promoting this to potential feature. I agree with much of what you say, but the schema does not change based on anything other than Microsoft's development team adding new properties to or removing them from the schema. And if it were determined at runtime, it would suggest that the website is in some kind of shell that emits the properties every time someone visits it, being dynamic and all. 🤗

[vs-code-engineering]

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!