From 89ae4ca9a3044e5f4a7f9ed147443b23a06743b9 Mon Sep 17 00:00:00 2001 From: Kirill Bulatov Date: Tue, 18 Mar 2025 23:46:11 +0200 Subject: [PATCH] Fix debugger docs a bit (#27026) Tried adding a custom debugging tasks to discover two more required properties missing from the docs. Release Notes: - N/A --- crates/project/src/debugger/README.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/crates/project/src/debugger/README.md b/crates/project/src/debugger/README.md index 0e8809492698ff6c599b42f9c6bcd0b551f9d12a..bb992867a0a6f5e79f59e4de5c165eb013956d32 100644 --- a/crates/project/src/debugger/README.md +++ b/crates/project/src/debugger/README.md @@ -38,7 +38,7 @@ To create a custom debug configuration you have to create a `.zed/debug.json` fi [ { // The label for the debug configuration and used to identify the debug session inside the debug panel - "label": "Example Start debugger config" + "label": "Example Start debugger config", // The debug adapter that Zed should use to debug the program "adapter": "custom", // Request: defaults to launch @@ -55,7 +55,11 @@ To create a custom debug configuration you have to create a `.zed/debug.json` fi // initialize_args: This field should contain all the adapter specific initialization arguments that are directly send to the debug adapter "initialize_args": { // "stopOnEntry": true // e.g. to stop on the first line of the program (These args are DAP specific) - } + }, + // connection: the connection that a custom debugger should use + "connection": "stdio", + // The cli command used to start the debug adapter e.g. `python3`, `node` or the adapter binary + "command": "path_to_cli" } ] ```