This commit is contained in:
Andre Weinand 2016-12-12 15:40:20 +01:00
Родитель 60cbfb1f4e
Коммит d0b814f256
1 изменённых файлов: 1 добавлений и 1 удалений

Просмотреть файл

@ -419,7 +419,7 @@ Ever since the text document allows to ask for a [word-range](https://github.com
## Debugger Extension Authoring
- In the `launch.json` the top level `debugServer` attribute has been deprecated (and support for it will be removed in the February milestone). Instead the `debugServer` attribute has to be specified per launch configuration. More details can be found [here](https://github.com/Microsoft/vscode/issues/13783).
- Debugger extensions can now contribute debug configuration snippets which will get surfaced in `launch.json` file as explained in section "Adding Individual Launch Configurations". This can be done using the regular syntax for contributing snippets to VSCode, but as a "configurationSnippets" attribute inside the "debuggers" section of the `package.json`. An example of how Mock Debug is contributing debug configuration snippets this can be found [here](https://github.com/Microsoft/vscode-mock-debug/blob/master/package.json#L71)
- Debugger extensions can now contribute launch configuration snippets which will get surfaced in `launch.json` as explained in section "Adding Individual Launch Configurations". This can be done using the regular syntax for contributing snippets to VS Code, but as a `configurationSnippets` attribute inside the `debuggers` section of the `package.json`. An example of how Mock Debug is contributing debug configuration snippets can be found [here](https://github.com/Microsoft/vscode-mock-debug/blob/master/package.json#L71).
### VS Code Debug Protocol