Feature Request
I would like Datastar to provide a Zed extension with language support and snippets for Datastar attributes and expressions.
The repository already contains integrations for VS Code and IntelliJ, but Zed users do not have equivalent, installable support. Without an extension, users must maintain their own snippets and rely on generic HTML highlighting, which duplicates Datastar’s canonical definitions and can fall out of sync as Datastar evolves.
A useful initial scope would be:
- syntax highlighting for Datastar attributes and expressions in HTML and supported template files;
- snippets for Datastar attributes and actions, using the existing VS Code extension data as a baseline where practical;
- packaging and publication through Zed’s extension registry.
This follows #1172, where Zed was mentioned alongside other editors. That issue was primarily about Helix and LSP-based autocompletion and is now closed. This request is specifically for a concrete Zed extension contribution.
If maintainers agree with this direction, I am planning to work on the implementation and open a pull request against develop once the preferred scope and repository location are agreed.
Before starting, I would appreciate guidance on:
- Whether the extension should live in this repository, for example under
tools/zed-extension, or in a separate repository.
- Whether feature parity with the existing VS Code extension is the preferred baseline.
- Which markup and template languages should be included in the initial version.
The alternative is to publish personal Zed snippets and configuration separately, but that would be less discoverable and would not provide a single versioned integration that can track Datastar changes.
Datastar Version
v1.0.2
LLM Use Disclosure
This issue was drafted with assistance from an OpenAI language model.
Prompts used:
I want to raise a feature request on upstream asking for a Zed extension providing the Datastar language and snippets and say that I am planning on working on it.
Ok given the above, and given contributing.md says Pull Requests: Always open an issue to discuss your idea before submitting a pull request. Pull requests must be made to the develop branch, have a descriptive title and clearly describe the problem and solution. If the pull request adds or changes behavior, appropriate justification must be provided, and documentation and examples should be updated accordingly. Would it make sense to create a new issue stating that I am planning on working on it, or work on it and create a PR that addresses the existing issue?
Accuracy and relevance review:
The generated draft was checked against the current feature-request template, CONTRIBUTING.md, issue #1172 and its maintainer response, the existing VS Code extension under tools/vscode-extension, and current Zed extension documentation. Before this issue was submitted, I personally reviewed the complete draft for accuracy and relevance, confirmed that it matches my intended request and contribution plan, and approved the final wording.
Feature Request
I would like Datastar to provide a Zed extension with language support and snippets for Datastar attributes and expressions.
The repository already contains integrations for VS Code and IntelliJ, but Zed users do not have equivalent, installable support. Without an extension, users must maintain their own snippets and rely on generic HTML highlighting, which duplicates Datastar’s canonical definitions and can fall out of sync as Datastar evolves.
A useful initial scope would be:
This follows #1172, where Zed was mentioned alongside other editors. That issue was primarily about Helix and LSP-based autocompletion and is now closed. This request is specifically for a concrete Zed extension contribution.
If maintainers agree with this direction, I am planning to work on the implementation and open a pull request against
developonce the preferred scope and repository location are agreed.Before starting, I would appreciate guidance on:
tools/zed-extension, or in a separate repository.The alternative is to publish personal Zed snippets and configuration separately, but that would be less discoverable and would not provide a single versioned integration that can track Datastar changes.
Datastar Version
v1.0.2
LLM Use Disclosure
This issue was drafted with assistance from an OpenAI language model.
Prompts used:
Accuracy and relevance review:
The generated draft was checked against the current feature-request template,
CONTRIBUTING.md, issue #1172 and its maintainer response, the existing VS Code extension undertools/vscode-extension, and current Zed extension documentation. Before this issue was submitted, I personally reviewed the complete draft for accuracy and relevance, confirmed that it matches my intended request and contribution plan, and approved the final wording.