Paul Young
Paul Young
Perhaps I'm misunderstanding how `react-test-renderer` and/or snapshots work, but I thought the test renderer did a shallow render. In that case, I don't know why I'm seeing internals of the...
(This is a obviously a separate question to the original issue)
For anyone else experiencing this issue, my workaround is to pass `@` to the included partial: **bar.ect** ``` ect ``` **output** ``` json { "foo": "foo", "baz": "baz" } ```
I'm finding that I need this too.
Reproducable on http://ectjs.com: 
The issue seems to stem the tracking of named blocks being somewhat naïve. https://github.com/baryshev/ect/blob/0edfa8c4283153128363b53878e1bbdc4e6211c5/lib/ect.js#L303-L306 In my example, a block with the same name already exists (because I'm using the partial...
> This is problem of coffee-script itself, not ECT. > You need to do something similar to this: > > ``` coffeescript > for i in [0..10] > do (i)...
> And yes, blocks are not a good idea here. What do you mean by that?
Thanks for the tip. Seems to be the best option as a workaround for now.
This appears to fix #83 but without a test suite it's impossible to know the impact of these changes.