ES6 problem in 2.1.1 handlebar helper that worked fine in 1.8.2

Reply to ES6 problem in 2.1.1 handlebar helper that worked fine in 1.8.2 on Sun, 05 Aug 2018 11:43:01 GMT

MolallaComm — Sun, 05 Aug 2018 11:43:01 GMT

I have a handlebar helper function:

function SummarysForContact(map, name) { 
    var summary = "";  
    var byname = map.get(name);
    byname.forEach(function(val, key) {
        summary += 'Trouble # ' + key.toString() + " - " + val.Minutes + " minutes \r\n";
        summary += "\r\n";
        summary += val.Summary.replace(/(?:\r\n|\r|\n)/g, '
');
        summary += "
\r\n";
    });

    return summary;
}

The first parameter is an ES6 Map - works fine in 1.8.2 .NET embedded - does not work in 2.1.1 native node version. Give this following error:

Error while executing templating engine. map.get is not a function. Error on line 3:22.

  1 | function SummarysForContact(map, name) { 
  2 |     var summary = "";  
> 3 |     var byname = map.get(name);
    |                      ^
  4 |     byname.forEach(function(val, key) {
  5 |         summary += 'Trouble # ' + key.toString() + " - " + val.Minutes + " minutes \r\n";
  6 |         summary += "\r\n";

Reply to ES6 problem in 2.1.1 handlebar helper that worked fine in 1.8.2 on Invalid Date

jan_blaha — Invalid Date

Try to print out what is the map parameter.
How do you pass it to the helper function?

There should me no change regarding this in v1.8.2 => v2.1.1

Reply to ES6 problem in 2.1.1 handlebar helper that worked fine in 1.8.2 on Invalid Date

MolallaComm — Invalid Date

The simplest template/script/helper I could make to reproduce:

https://cdn.rawgit.com/olton/Metro-UI-CSS/master/build/css/metro.min.css">


{{#each Contacts}}
{{ContactName}} - {{NumMinutes}} minutes on {{NumTickets}} tickets
{{{SummarysForContact ../Summarys ContactName}}}
{{/each}}

function SummarysForContact(map, name) {
var summary = "";

summary += `map = ${map}, name = ${name}`;
/*
var byname = map.get(name);
byname.forEach(function(val, key) {
    summary += `key = ${key}, val = ${val}`;
});
*/

return summary;

}

function beforeRender(req, res, done) {
req.data.Contacts = [{ ContactName: "User1", NumMinutes: 100, NumTickets: 11}, { ContactName: "User2", NumMinutes: 200, NumTickets: 21 }];
req.data.Summarys = new Map();

var submap1 = new Map();  
submap1.set(11, "description for 11"); 
submap1.set(12, "description for 12");
req.data.Summarys.set("User1", submap1);

var submap2 = new Map();
submap2.set(21, "description for 21"); 
submap2.set(22, "descripton for 22");
req.data.Summarys.set("User2", submap2);

done();

}

Reply to ES6 problem in 2.1.1 handlebar helper that worked fine in 1.8.2 on Invalid Date

jan_blaha — Invalid Date

The default config file sets up jsreport to evaluate templating engines in extra process. This means we serialize and deserialize data when running stcript or templating engine. This means we loose types like map in this process.

To make your code working you can configure jsreport to run scripts and templating engines in the same process as the whole application.

{
"templatingEngines": {
    "timeout": 10000,
    "strategy": "in-process"
  }
}

Another option is to avoid using extra types like Map which cannot be simply serialized/deserialized.
In this case you can probably use simple plain object.

Reply to ES6 problem in 2.1.1 handlebar helper that worked fine in 1.8.2 on Invalid Date

MolallaComm — Invalid Date

Thanks for following up on this - sure enough using plain old object fixed it! I think i used map originally just to see if newer ES5/6 stuff worked which i guess it does minus this serialization issue.