You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: extensions/json-language-features/server/README.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ The JSON language server has the following dependencies on the client's capabili
44
44
45
45
The client can send the following initialization options to the server:
46
46
47
-
-`provideFormatter: boolean | undefined`. If defined, the value defines wheter the server provides the `documentRangeFormattingProvider` capability on initialization. If undefined, the setting `json.format.enable` is used to determined wheter formatting is provided. The formatter will then be registered through dynamic registration. If the client does not support dynamic registration, no formatter will be available.
47
+
-`provideFormatter: boolean | undefined`. If defined, the value defines whether the server provides the `documentRangeFormattingProvider` capability on initialization. If undefined, the setting `json.format.enable` is used to determine whether formatting is provided. The formatter will then be registered through dynamic registration. If the client does not support dynamic registration, no formatter will be available.
48
48
-`handledSchemaProtocols`: The URI schemas handles by the server. See section `Schema configuration` below.
49
49
50
50
### Settings
@@ -60,7 +60,7 @@ The server supports the following settings:
60
60
-`format`
61
61
-`enable`: Whether the server should register the formatting support. This option is only applicable if the client supports *dynamicRegistration* for *rangeFormatting* and `initializationOptions.provideFormatter` is not defined.
62
62
-`schema`: Configures association of file names to schema URL or schemas and/or associations of schema URL to schema content.
63
-
- `fileMatch`: an array or file names or paths (separated by `/`). `*` can be used as a wildcard.
63
+
- `fileMatch`: an array of file names or paths (separated by `/`). `*` can be used as a wildcard.
64
64
- `url`: The URL of the schema, optional when also a schema is provided.
65
65
- `schema`: The schema content.
66
66
@@ -99,9 +99,9 @@ To find the schema for a given JSON document, the server uses the following mech
99
99
- The settings define a schema association based on the documents URL. Settings can either associate a schema URL to a file or path pattern, and they can directly provide a schema.
100
100
- Additionally, schema associations can also be provided by a custom 'schemaAssociations' configuration call.
101
101
102
-
Schemas are identified by URLs. To load the content of a schema, the JSON language server either tries to load from that URI or path itself, or delegates to the client.
102
+
Schemas are identified by URLs. To load the content of a schema, the JSON language server either tries to load from that URI or path itself or delegates to the client.
103
103
104
-
The `initializationOptions.handledSchemaProtocols` initialization option defines which URLs are handled by the server. Requests for all other URIs are send to the client.
104
+
The `initializationOptions.handledSchemaProtocols` initialization option defines which URLs are handled by the server. Requests for all other URIs are sent to the client.
105
105
106
106
`handledSchemaProtocols` is part of the initialization options and can't be changed while the server is running.
107
107
@@ -121,7 +121,7 @@ If `handledSchemaProtocols` is not set, the JSON language server will load the f
121
121
122
122
#### Schema content request
123
123
124
-
Requests for schemas with URLs not handled by the server are forwarded to the client through an LSP request. This request is a JSON language serverspecific, non-standardized, extension to the LSP.
124
+
Requests for schemas with URLs not handled by the server are forwarded to the client through an LSP request. This request is a JSON language server-specific, non-standardized, extension to the LSP.
125
125
126
126
Request:
127
127
- method: 'vscode/content'
@@ -130,12 +130,12 @@ Request:
130
130
131
131
#### Schema content change notification
132
132
133
-
When the client is aware that a schema content has changed, it will notify the server through a notification. This notification is a JSON language serverspecific, non-standardized, extension to the LSP.
133
+
When the client is aware that a schema content has changed, it will notify the server through a notification. This notification is a JSON language server-specific, non-standardized, extension to the LSP.
134
134
The server will, as a response, clear the schema content from the cache and reload the schema content when required again.
135
135
136
136
#### Schema associations notification
137
137
138
-
In addition to the settings, schemas associations can also be provided through a notification from the client to the server. This notification is a JSON language serverspecific, non-standardized, extension to the LSP.
138
+
In addition to the settings, schemas associations can also be provided through a notification from the client to the server. This notification is a JSON language server-specific, non-standardized, extension to the LSP.
0 commit comments