I'm creating a package that wraps the two core methods for setting and retrieving helpers on a template – Template.prototype.helpers and Blaze._getTemplateHelper (even if the latter isn't official) – in order to make the two methods reactive, like ReactiveDict.
This way, a helper that is added after the template is rendered (or while it is being rendered), will still become active. This is discussed here.
The problem with wrapping the two methods is if someone writes directly to the __helpers map, and I think your package is by far the most popular package that does this.
Please merge this tiny pull request to support the pattern above. Thanks :)
I'm creating a package that wraps the two core methods for setting and retrieving helpers on a template –
Template.prototype.helpers
andBlaze._getTemplateHelper
(even if the latter isn't official) – in order to make the two methods reactive, like ReactiveDict.This way, a helper that is added after the template is rendered (or while it is being rendered), will still become active. This is discussed here.
The problem with wrapping the two methods is if someone writes directly to the
__helpers
map, and I think your package is by far the most popular package that does this.Please merge this tiny pull request to support the pattern above. Thanks :)