Nils Knappmeier

Sorry, I haven't had a thorough look yet. But I think something similar is part of our plans avoid security vulnerabilities in the future. I would like to defer until...

I would like to merge this, but the API is not what I would want to have. I have to do a general API discusssion with @wycats for overriding this...

In #1559, I added the `hooks` property to the runtime. I'm still not confident about a good name for the function(s) to register a hook * `Handlebars.on('escapeExpression', (expression) => ...))`...

@thekiwi would it be OK for you to have a runtime option to override "escapeExpression"?

It would be something like ```js const template = Handlebars.compile('{{name}}'); const output = template({ name: 'Jonny "the hound" Walker' }, { hooks: { escapeExpression: string => string.replace(/(["'\\])/g,'\\$1') } } ```

The easiest way is to * create a custom helper (e.g. `arr`) that returns an array from a dynamic lists of param (be sure to omit the last argument, because...

@wycats wants a formal spec of the existing language before adding new language features (#1277). But currently, nobody is really working on one, so I don't see any progress on...

nested_property.bar is not a helper call, but a property access. When accessing top-level properties, there is no syntactical distinction between helpers and property access, but helpers cannot contain a ".",...

Changing this probably reaches down into compiler. I am not sure what exactly needs to be changed. @wycats What do you think of this? A hook to be called when...

no, it makes sense, but I haven't got the time to work on it and it seems like @wycats is also busy. Besides, we want a spec (#1277) before adding...