LBF38andFinn Evers
46f16c7502
Add documentation for snippets in extensions. Feel free to change the wording or add more content. Before you mark this PR as ready for review, make sure that you have: - [ ] Added a solid test coverage and/or screenshots from doing manual testing - [ ] Done a self-review taking into account security and performance aspects - [ ] Aligned any UI changes with the [UI checklist](https://github.com/zed-industries/zed/blob/main/CONTRIBUTING.md#uiux-checklist) Release Notes: - N/A --------- Co-authored-by: Finn Evers <finn.evers@outlook.de>
28 lines
927 B
Markdown
28 lines
927 B
Markdown
---
|
|
title: Snippets
|
|
description: "Snippets for Zed extensions."
|
|
---
|
|
|
|
# Snippets
|
|
|
|
Extensions may provide snippets for one or more languages.
|
|
|
|
Each file containing snippets can be specified in the `snippets` field of the `extensions.toml` file.
|
|
|
|
The referenced path must be relative to the `extension.toml`.
|
|
|
|
## Defining Snippets
|
|
|
|
A given extension may provide one or more snippets. Each snippet must be registered in the `extension.toml`.
|
|
|
|
Zed matches snippet files based on the lowercase name of the language (e.g. `rust.json` for Rust).
|
|
You can use `snippets.json` as a file name to define snippets that will be available regardless of the current buffer language.
|
|
|
|
For example, here is an extension that provides snippets for Rust and TypeScript:
|
|
|
|
```toml
|
|
snippets = ["./snippets/rust.json", "./snippets/typescript.json"]
|
|
```
|
|
|
|
For more information on how to create snippets, see the [Snippets documentation](../snippets.md).
|