Closed alexef closed 9 years ago
Just noticed this as well. Any ideas how to fix it? Still trying to remember how I had set this up so long ago haha
I haven't had a chance to get familiar with Handlebars 2.0. Sorry! I haven't forgotten about this issue, I just haven't had time to look into it yet. I don't use v2.0 personally yet so it's hard to keep it high on my list of priorities.
I'll certainly welcome a PR if anyone wants to take a stab at figuring it out though!
Oops didn't mean to close. Re-opening.
Ok I got it to work. Really easy actually haha. I'll post a write-up / pull request soon
Ok all you really need to do is:
So the only change really is changing the package.json to 2.0.0
Is this expected to break compatibility with <2.0 Handlebars?
Also thank you for looking into it!
Yeah.
"Precompiler output has changed, which means your 1.x precompiled templates would not be compatible with Handlebars 2.x runtime, as well as 2.x runtime will be not compatible with old templates. You should update precompiler, update runtime and update all templates."
"Partials no longer have access to parent context (../), but now can accept hash as argument and has access to the root context through @root variable. So look at your partials for using ../ and change it to using local data, passed to partial as argument."
We are going to be finally merging this update very soon. There is an open pull request if you want to help test please leave comments there. Closing issue. Sorry for the very long wait time! I no longer use this myself so it has fallen to the bottom of my ever-growing to-do list.
Latest release of handlebars breaks template compatibility with v1.3.0