Larry Davis

@DominikGuzei's version worked beautifully for my use case and is available on npm as [`ase-utils`](https://www.npmjs.com/package/ase-utils)!

Yeah, I think it ought to as we should be looking for `{{` and `}}` not `{` and `}`. For now, you can escape each `{` and `}` with `\{`...

@devel-pa good stuff! It would be great if you tested and maintained this, though I'm not sure what the demand is like now.

@cespare you can accomplish the equality comparison with a quick helper: Helper: ``` js function eq(a, b) { return a === b; } ``` Template: ``` html Yay! ``` Output:...

## Problems with this proposal I haven't worked enough with dust.js and velocity to have seen this in practice, so forgive my ignorance please! I see a couple problems: ###...

DOMly has zero client-side runtime or dependencies. Introducing something like this would at least necessitate including a `flatten(object)` utility function to do the flattening (else the DOMly template functions would...

I see, so block scoping, effectively. I think I have a strategy to accomplish this with a little preprocessing and a little helper method inside, I'll report back after I...

Currently, DOMly creates a number of variables are named `data_0`, `data_1` with the data for each block, then assigns `data = data_1` as necessary. What we need to do is...

@georgkoester, check out the [`issue/22` branch](https://github.com/lazd/DOMly/tree/issue/22) for a solution! Basically, you can pass `useScope: true` to the compiler and you now have a magical variable, `scope`, that, when dereferenced i.e....

I pushed another branch ([issue/22-no-vars](https://github.com/lazd/DOMly/tree/issue/22-no-vars)) that removes the usage of `data_N` vars and relies on `scope` exclusively (things got a little dirty there for a bit, heh, sorry for the...