ZIm/crates/extension_api
Anthony Eid 1c9b818342
debugger: Use DAP schema to configure daps (#30833)
This PR allows DAPs to define their own schema so users can see
completion items when editing their debug.json files.

Users facing this aren’t the biggest chance, but behind the scenes, this
affected a lot of code because we manually translated common fields from
Zed's config format to be adapter-specific. Now we store the raw JSON
from a user's configuration file and just send that.

I'm ignoring the Protobuf CICD error because the DebugTaskDefinition
message is not yet user facing and we need to deprecate some fields in
it.

Release Notes:

- debugger beta: Show completion items when editing debug.json
- debugger beta: Breaking change, debug.json schema now relays on what
DAP you have selected instead of always having the same based values.

---------

Co-authored-by: Remco Smits <djsmits12@gmail.com>
Co-authored-by: Cole Miller <m@cole-miller.net>
Co-authored-by: Cole Miller <cole@zed.dev>
2025-05-22 05:48:26 -04:00
..
src debugger: Use DAP schema to configure daps (#30833) 2025-05-22 05:48:26 -04:00
wit debugger: Use DAP schema to configure daps (#30833) 2025-05-22 05:48:26 -04:00
build.rs chore: Fix several style lints (#17488) 2024-09-06 11:58:39 +02:00
Cargo.toml zed_extension_api: Fork new version of extension API (#30611) 2025-05-13 08:35:15 +00:00
LICENSE-APACHE Add initial support for defining language server adapters in WebAssembly-based extensions (#8645) 2024-03-01 16:00:55 -08:00
PENDING_CHANGES.md zed_extension_api: Start a list of pending changes (#16305) 2024-08-15 13:10:46 -04:00
README.md zed_extension_api: Release v0.5.0 (#29802) 2025-05-02 15:58:54 +00:00

The Zed Rust Extension API

This crate lets you write extensions for Zed in Rust.

Extension Manifest

You'll need an extension.toml file at the root of your extension directory, with the following structure:

id = "my-extension"
name = "My Extension"
description = "..."
version = "0.0.1"
schema_version = 1
authors = ["Your Name <you@example.com>"]
repository = "https://github.com/your/extension-repository"

Cargo metadata

Zed extensions are packaged as WebAssembly files. In your Cargo.toml, you'll need to set your crate-type accordingly:

[dependencies]
zed_extension_api = "0.5.0"

[lib]
crate-type = ["cdylib"]

Implementing an Extension

To define your extension, create a type that implements the Extension trait, and register it.

use zed_extension_api as zed;

struct MyExtension {
    // ... state
}

impl zed::Extension for MyExtension {
    // ...
}

zed::register_extension!(MyExtension);

Testing your extension

To run your extension in Zed as you're developing it:

  • Open the extensions view using the zed: extensions action in the command palette.
  • Click the Install Dev Extension button in the top right
  • Choose the path to your extension directory.

Compatible Zed versions

Extensions created using newer versions of the Zed extension API won't be compatible with older versions of Zed.

Here is the compatibility of the zed_extension_api with versions of Zed:

Zed version zed_extension_api version
0.186.x 0.0.1 - 0.5.0
0.184.x 0.0.1 - 0.4.0
0.178.x 0.0.1 - 0.3.0
0.162.x 0.0.1 - 0.2.0
0.149.x 0.0.1 - 0.1.0
0.131.x 0.0.1 - 0.0.6
0.130.x 0.0.1 - 0.0.5
0.129.x 0.0.1 - 0.0.4
0.128.x 0.0.1