handlebars 3.0 support

[mattkime]

changes are outlined here - https://github.com/wycats/handlebars.js/blob/master/release-notes.md#v300---february-10th-2015

additional template features are of particular interest.

[husayt]

Does anyone know if handlebars 3 already supported? If we just switch js library to handlebars,js 3 will it work?

[mattkime]

the handlebars js file is only used for hbs -> js compilation. rendering of templates uses java

[grnadav]

@mattkime I didn't understand from your reply whether it's supported or not.
Can one just set
handlebars.handlebarsJsFile("/handlebars-v3.0.0.js");
and expect it to work?

[mattkime]

@grnadav if you're using handlebars.java to render hbs templates then that code won't change a thing. the js file is only used to compile hbs files into javascript. this is useful when rendering hbs on the client as its faster and doesn't require the full handlebars.js functionality.

[grnadav]

@mattkime Got it. Thanks!

[jknack]

Guys,

I will release a 2.1.0 tomorrow, which has partials params #350 & #357.

But I'm not sure what else is new in terms of language feature, so do me a favor and open new issues describing what else need to be done to create a 3.0.0 compatible version.

For now, I will close this issue bc it is too vague.

Thanks

[husayt]

Thanks for latest updates @jknack .

In terms of new features from hbs.js3 from version 2 I can see these:

• #906 - Block Params
• #941 - Add support for dynamic partial names
• #892 - Chained else blocks
• #910 - @last and other each changes
• #805 - Strict Mode
• #886 - Add SafeString to context (or use duck-typing)
• #887 - Handlebars.noConflict() option?
• # - @DaTa methods can now have helper parameters passed to them
• #940, #964 - Add missing reserved words so compiler knows to use array syntax:

Here is a full release notes for hbs.js:
https://github.com/wycats/handlebars.js/blob/master/release-notes.md

I am not sure which of these are already supported. Some of them might not even make sense for Java environment.

As hbs.js is evolving it will be difficult to maintain 1-1 compatibility. What might help is to be able to run hbs.js unit tests as part of hbs-java unit tests.

Again thanks for great work, it is very appreciated.