These VS Code-specific properties are currently top-level. The proposal is to introduce a vscode property for VS Code-specific configuration and move these two properties there.
We can copy the properties in the schema, keeping the old properties as 'deprecated' for compatibility.
One open question is how we can include runtime-specific parts of the JSON schema. For those runtimes we know of, we can reference or inline the schema. For now I suggest to keep these properties in the same schema file.
Interestingly settings and extensions also apply to Codespaces which already has a codespaces property for its own configuration.
/cc @bamurtaugh @Chuxel @jkeech
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4