Yehowshua/ZIm
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: Update manifest keys in debugger extension docs (#33085)

Browse source 
This is silly and caused at least one of our users a lot of confusion.

Closes #33040

Release Notes:

- N/A
This commit is contained in:
Piotr Osiewicz 2025-06-20 15:25:53 +02:00 • committed by GitHub
parent c02e249ecb
commit c9e5ff21a1
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 4 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/src/extensions/debugger-extensions.md
View file

@ -8,7 +8,7 @@ A given extension may provide one or more DAP servers.
Each DAP server must be registered in the `extension.toml`: Each DAP server must be registered in the `extension.toml`:
```toml ```toml
[debug-adapters.my-debug-adapter] [debug_adapters.my-debug-adapter]
# Optional relative path to the JSON schema for the debug adapter configuration schema. Defaults to `debug_adapter_schemas/$DEBUG_ADAPTER_NAME_ID.json`. # Optional relative path to the JSON schema for the debug adapter configuration schema. Defaults to `debug_adapter_schemas/$DEBUG_ADAPTER_NAME_ID.json`.
# Note that while this field is optional, a schema is mandatory. # Note that while this field is optional, a schema is mandatory.
schema_path = "relative/path/to/schema.json" schema_path = "relative/path/to/schema.json"
@ -72,7 +72,7 @@ Locators can (but don't have to) be agnostic to the debug adapter they are used
Your extension can define one or more debug locators. Each debug locator must be registered in the `extension.toml`: Your extension can define one or more debug locators. Each debug locator must be registered in the `extension.toml`:
```toml ```toml
[debug-locators.my-debug-locator] [debug_locators.my-debug-locator]
``` ```
Locators have two components. Locators have two components.

2
docs/src/extensions/developing-extensions.md
View file

@ -89,6 +89,8 @@ impl zed::Extension for MyExtension {
zed::register_extension!(MyExtension); zed::register_extension!(MyExtension);
``` ```
> `stdout`/`stderr` is forwarded directly to the Zed process. In order to see `println!`/`dbg!` output from your extension, you can start Zed in your terminal with a `--foreground` flag.
## Forking and cloning the repo ## Forking and cloning the repo
1. Fork the repo 1. Fork the repo