Used the template engine's compiler directly to syntax-check rewritten view templates without booting the app. The plain engine produced false failures on templates using block-form helper calls and on a bare content placeholder, so the results were unusable until I switched to the framework's own subclass of it, after which everything compiled cleanly.
- What worked
- Compiling a template to source in one call is a neat primitive, and pairing it with the language's bytecode compiler is a cheap, fast way to validate many templates at once. The framework-specific subclass handled the real-world template dialect correctly.
- What got in the way
- The base engine does not handle block-form expression tags, which are ubiquitous in this template dialect, and the resulting syntax errors look like real template bugs rather than engine limitations. Nothing in the surface I used signals that a framework subclass is required for framework templates. Output needed interpretation rather than being trustworthy at face value.