https://github.com/davidcornu/zed-haml
Haml template syntax support for Zed
https://github.com/davidcornu/zed-haml
Last synced: 3 months ago
JSON representation
Haml template syntax support for Zed
- Host: GitHub
- URL: https://github.com/davidcornu/zed-haml
- Owner: davidcornu
- Created: 2024-09-13T17:31:00.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2025-01-09T01:44:52.000Z (over 1 year ago)
- Last Synced: 2025-04-07T06:43:35.695Z (about 1 year ago)
- Language: Scheme
- Size: 21.5 KB
- Stars: 13
- Watchers: 3
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
- awesome-zed-extensions - Haml
README
# [Haml](https://haml.info/) syntax highlighting for [Zed](https://zed.dev/)
> [!NOTE]
> This extension is regularly published (https://zed.dev/extensions?query=haml) and can be installed directly from Zed.
>
> You will likely also want to install the [Ruby extension](https://github.com/zed-extensions/ruby) so that Ruby snippets within your HAML templates are correctly highlighted.
Based on https://github.com/vitallium/tree-sitter-haml
## Developing
Clone this repository and [install it as a dev extension in Zed](https://zed.dev/docs/extensions/developing-extensions#developing-an-extension-locally).
The complete docs on extension development are here: https://zed.dev/docs/extensions/developing-extensions.
## Releasing
1. Create a new commit which updates the `version` field in `extensions.toml` and commit it to `main`
2. Tag that commit with the new version number (e.g. `v0.0.1`)
```
git tag v0.0.1
git push origin v0.0.1
```
3. Create a new GitHub release (https://github.com/davidcornu/zed-haml/releases/new) for that tag. The automatically-generated release notes should suffice.
4. In https://github.com/zed-industries/extensions/
1. Update the `version` field in `extensions.toml` under `[haml]`
2. Run `git submodule update --remote --merge extensions/haml`
3. Make sure the ref returned by `git submodule status extensions/haml` is the correct tag
4. Commit the above and open a PR