Mike Gerwitz
daa8c6967b
I had hoped this would be considerably easier to implement, but there are some confounding factors. First of all: this accomplishes the initial task of getting nested template applications and definitions re-output in the `xmli` file. But to do so successfully, some assumptions had to be made. The primary issue is that of scope. The old (XSLT-based) TAME relied on the output JS to handle lexical scope for it at runtime in most situations. In the case of the template system, when scoping/shadowing were needed, complex and buggy XPaths were used to make a best effort. The equivalent here would be a graph traversal, which is not ideal. I had begun going down the rabbit hole of formalizing lexical scope for TAMER with environments, but I want to get this committed and working first; I've been holding onto this and breaking off changes for some time now. DEV-13708 |
||
|---|---|---|
| .. | ||
| air | ||
| graph | ||
| .gitignore | ||
| air.rs | ||
| error.rs | ||
| graph.rs | ||
| mod.rs | ||