Ilya Brin

P.S. I think since our last discussion, there's been an additional feature added - "internal data". This is so that special data can be passed along, that's not visible/accessible from...

I think this may be suspect? https://github.com/jknack/handlebars.java/blob/master/handlebars/src/main/java/com/github/jknack/handlebars/Options.java#L532-L539

ah, actually I think it's this! https://github.com/jknack/handlebars.java/blob/master/handlebars/src/main/java/com/github/jknack/handlebars/Context.java#L96-L98 when the second `EachHelper` creates its child context (https://github.com/jknack/handlebars.java/blob/master/handlebars/src/main/java/com/github/jknack/handlebars/helper/EachHelper.java#L64), the child context will be a `ParentFirst` context (because the current context from https://github.com/jknack/handlebars.java/blob/master/handlebars/src/main/java/com/github/jknack/handlebars/helper/EachHelper.java#L60...

hmm... are you saying this is expected/correct behavior, and same in handlebars.js? it seems strange that not using block params completely messes up the whole context...

it works fine in handlebars.js so i think it's a bug here? fiddle: https://jsfiddle.net/L3emzo2k/5/

i see... this test fails: https://github.com/jknack/handlebars.java/blob/master/handlebars/src/test/java/com/github/jknack/handlebars/BlockParamsTest.java#L70-L87

Looking at the test, I'm not quite sure why it expects that output.... it registers the helper `goodbyes`: ``` $("goodbyes", new Helper() { int value = 1; @Override public Object...

hmm... you're right.. handlebars.js has this weird behavior.... https://jsfiddle.net/L3emzo2k/6/

what i find strange though is that the `each` sample works in handlebars.js but breaks here.... can't figure out why...

opened an issue against hbars... https://github.com/wycats/handlebars.js/issues/1484