Skip to content

Commit 93a182c

Browse files
authored
Fix indent
1 parent 00662f2 commit 93a182c

File tree

1 file changed

+27
-27
lines changed

1 file changed

+27
-27
lines changed

docs/extensibility/adding-an-lsp-extension.md

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -123,10 +123,10 @@ The LSP does not include specification on how to provide text colorization for l
123123

124124
4. Create a *.pkgdef* file and add a line similar to this:
125125

126-
```xml
127-
[$RootKey$\TextMate\Repositories]
128-
"MyLang"="$PackageFolder$\Grammars"
129-
```
126+
```xml
127+
[$RootKey$\TextMate\Repositories]
128+
"MyLang"="$PackageFolder$\Grammars"
129+
```
130130

131131
5. Right-click on the files and select **Properties**. Change the **Build** action to **Content** and the **Include in VSIX** property to true.
132132

@@ -286,31 +286,31 @@ Follow these steps below to add support for settings to your LSP language servic
286286

287287
1. Add a JSON file (for example, *MockLanguageExtensionSettings.json*) in your project that contains the settings and their default values. For example:
288288

289-
```json
290-
{
291-
"foo.maxNumberOfProblems": -1
292-
}
293-
```
289+
```json
290+
{
291+
"foo.maxNumberOfProblems": -1
292+
}
293+
```
294294
2. Right-click on the JSON file and select **Properties**. Change the **Build** action to "Content" and the "Include in VSIX' property to true.
295295

296296
3. Implement ConfigurationSections and return the list of prefixes for the settings defined in the JSON file (In Visual Studio Code, this would map to the configuration section name in package.json):
297297

298-
```csharp
299-
public IEnumerable<string> ConfigurationSections
300-
{
301-
get
302-
{
303-
yield return "foo";
304-
}
305-
}
306-
```
298+
```csharp
299+
public IEnumerable<string> ConfigurationSections
300+
{
301+
get
302+
{
303+
yield return "foo";
304+
}
305+
}
306+
```
307307

308308
4. Add a .pkgdef file to the project (add new text file and change the file extension to .pkgdef). The pkgdef file should contain this info:
309309

310-
```xml
310+
```xml
311311
[$RootKey$\OpenFolder\Settings\VSWorkspaceSettings\[settings-name]]
312312
@="$PackageFolder$\[settings-file-name].json"
313-
```
313+
```
314314

315315
Sample:
316316
```xml
@@ -334,13 +334,13 @@ Follow these steps below to add support for settings to your LSP language servic
334334
2. User adds a file in the *.vs* folder called *VSWorkspaceSettings.json*.
335335
3. User adds a line to the *VSWorkspaceSettings.json* file for a setting the server provides. For example:
336336

337-
```json
338-
{
339-
"foo.maxNumberOfProblems": 10
340-
}
341-
```
342-
### Enabling diagnostics tracing
343-
Diagnostics tracing can be enabled to output all messages between the client and server, which can be useful when debugging issues. To enable diagnostic tracing, do the following:
337+
```json
338+
{
339+
"foo.maxNumberOfProblems": 10
340+
}
341+
```
342+
### Enabling diagnostics tracing
343+
Diagnostics tracing can be enabled to output all messages between the client and server, which can be useful when debugging issues. To enable diagnostic tracing, do the following:
344344

345345
4. Open or create the workspace settings file *VSWorkspaceSettings.json* (see "User editing of settings for a workspace").
346346
5. Add the following line in the settings json file:

0 commit comments

Comments
 (0)