Fix JSON schema configuration in multi root workspaces (#173169)

[json] add folderUri to SchemaAssociation and schema setting
This commit is contained in:
Martin Aeschlimann
2023-02-02 22:36:41 +01:00
committed by GitHub
parent 262ab0e7bf
commit bd9ac7a089
5 changed files with 29 additions and 71 deletions

View File

@@ -67,7 +67,8 @@ The server supports the following settings:
- `schemas`: Configures association of file names to schema URL or schemas and/or associations of schema URL to schema content.
- `fileMatch`: an array of file names or paths (separated by `/`). `*` can be used as a wildcard. Exclusion patterns can also be defined and start with '!'. A file matches when there is at least one matching pattern and the last matching pattern is not an exclusion pattern.
- `url`: The URL of the schema, optional when also a schema is provided.
- `schema`: The schema content.
- `schema`: The schema content, optional
- `folderUri`: If provided, the association is only used if the document is located in the given folder (directly or indirectly)
- `resultLimit`: The max number of color decorators and outline symbols to be computed (for performance reasons)
- `jsonFoldingLimit`: The max number of folding ranges to be computed for json documents (for performance reasons)
- `jsoncFoldingLimit`: The max number of folding ranges to be computed for jsonc documents (for performance reasons)
@@ -170,6 +171,10 @@ interface ISchemaAssociation {
* A match succeeds when there is at least one pattern matching and last matching pattern does not start with '!'.
*/
fileMatch: string[];
/**
* If provided, the association is only used if the validated document is located in the given folder (directly or indirectly)
*/
folderUri?: string;
/*
* The schema for the given URI.
* If no schema is provided, the schema will be fetched with the schema request service (if available).