Parser feature matrix
Parser feature matrix
Section titled “Parser feature matrix”Source of truth
Section titled “Source of truth”- Parser module scope notes:
crates/vox-compiler/src/parser/mod.rs - Parser descent implementation:
crates/vox-compiler/src/parser/descent/
Covered in canonical parser
Section titled “Covered in canonical parser”fn,pub fntype,pub typeimportcomponent(UI component declaration; emits React/TSX)server,query,mutation(bare keywords)@loadingtable,index(bare keywords)tool(bare keyword); legacy@mcp.tool/@toolstill parse but emitvox/decorator/mcp-tool-deprecated@test@v0actor,workflow,activity- HTTP route declarations (
http get/post/put/delete) routes { }(router shim generation)- JSX tags and expressions
- Expression operators including pipeline (
|>)
Retired (hard parser error)
Section titled “Retired (hard parser error)”@island— retired 2026-05-03; usecomponentinstead@endpoint(kind: server|query|mutation)— retired; use bareserver/query/mutation
Explicitly out of parser scope (current)
Section titled “Explicitly out of parser scope (current)”@page@partial@theme@layout@i18n@schema@action
Implications
Section titled “Implications”- Out-of-scope declarations increase lowering/codegen coupling and can create parser/docs drift.
- Roadmap target is to pull these into canonical parser/typed-HIR coverage to reduce cross-stage boilerplate.
Near-term verification
Section titled “Near-term verification”- Keep parser tests aligned with this matrix.
- Fail CI when docs and parser scope diverge for declared feature support.