slhx agent
df0fabd4fb
Add repo-local northstars and ready slices for testing strategy, LSP/editor completion, and hemplate highlighting boundaries.
1.3 KiB
1.3 KiB
id, type, status, parent, title, refs
| id | type | status | parent | title | refs | |||
|---|---|---|---|---|---|---|---|---|
| SLICE-0011 | slice | ready | NS-0003 | Add hemplate highlighting fixtures and query tests |
|
Objective
Create repo-owned highlighting fixtures that prove documented hemplate syntax receives stable captures while ordinary HTML remains handled by existing HTML tooling.
Authority
docs/hemplate-syntax.md is the syntax authority; docs/editor-support.md says highlighting is HTML first with hemx overlays.
Close when
- Fixtures cover text insertion, trusted HTML insertion, dynamic attributes,
h-if,h-for,h-key,h-match,h-case,data-hemx-root,data-hemx-slot,data-hemx-form, anddata-hemx-handle. - Tests or golden outputs verify capture names for those tokens.
- The test path is repo-owned and does not require publishing a VS Code/Cursor/Neovim package.
Verification
- Preferred future command: a repo-owned tree-sitter/query fixture test, once the crate/tool location is chosen.
- Until then, manual proof must name the exact editor/query runner and fixture.
Non-goals
- Do not parse Rust expressions inside
{+ +}beyond highlighting delimiters/expression region. - Do not make highlights responsible for diagnostics or completion.
Evidence
The fixture list maps directly to the documented syntax surface.