Topics created by gosanefr

I understand the concern and I used to prefer using jsrender as well.
However, Handlebars is just much more popular so we had to target our focus primarily on that. The Handlebars can be more chatty and less natural, but in the end you will reach your goals without big troubles.

Here are some answers to your questions, but you can typically find the answers quickly at StackOverflow or in the handlebars docs.

jsrender lets you do the tests directly inside the report like so : {{if someValue >= 2}}print this{{else}}print that{{/if}}. It seems that Handlebars requires to write a function for every single test. Did I miss something?

https://stackoverflow.com/questions/8853396/logical-operator-in-a-handlebars-js-if-conditional

it seems that jsrender lets you declare "variables" that you can use throughout the
templates (with {{* someVar = 2}} ). Does Handlebars provide such a feature?

You can use with helper, perhaps
https://handlebarsjs.com/guide/builtin-helpers.html#with
https://playground.jsreport.net/w/anon/P4y_7rdV

I like jsrender's itemVar feature that lets you define an alias rather than using the clumsy ../../../field. This is just comfort and readability so I can live without it.

This can be done with bloc parameters
https://handlebarsjs.com/guide/block-helpers.html#block-parameters

Thanks for the quick answer. I will consider going back to Handlebars but the fact that you have to write a function for every single test is really annoying (rather than directly doing something like {{if field>=2}}...{{/if}}). I will create a new thread on the question.