From 84392fbc2f70d4ab648887b4f713e59b2e5aaffe Mon Sep 17 00:00:00 2001 From: uncenter <47499684+uncenter@users.noreply.github.com> Date: Mon, 16 Dec 2024 16:11:32 -0500 Subject: [PATCH] docs: Use preferred `languages` instead of deprecated `language` field (#22107) Ref https://github.com/zed-industries/zed/issues/21994#issuecomment-2545988779, `language` is already deprecated but was still suggested in the docs here. Release Notes: - N/A --- docs/src/extensions/languages.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/extensions/languages.md b/docs/src/extensions/languages.md index 061496caf75812ffbd30484fc2518d976599cb35..9b414ab4fe8589b135aad10a6c95e0d0d47c668c 100644 --- a/docs/src/extensions/languages.md +++ b/docs/src/extensions/languages.md @@ -363,12 +363,12 @@ TBD: `#set! tag` Zed uses the [Language Server Protocol](https://microsoft.github.io/language-server-protocol/) to provide advanced language support. -An extension may provide any number of language servers. To provide a language server from your extension, add an entry to your `extension.toml` with the name of your language server and the language it applies to: +An extension may provide any number of language servers. To provide a language server from your extension, add an entry to your `extension.toml` with the name of your language server and the language(s) it applies to: ```toml [language_servers.my-language] name = "My Language LSP" -language = "My Language" +languages = ["My Language"] ``` Then, in the Rust code for your extension, implement the `language_server_command` method on your extension: