how to make a meteor template helper re-run/render after another template has rendered?

handlebars.js, javascript, meteor

Solution

You need a dependency in the template that you want to rerun. There are few possibilities, depending on what data you want to get.

For example, you can set a reactive marker in the `content` template that will notify `renderNav` that it's done with drawing.

Template.contentWidnow.rendered = function() {
    ...

    // Set this on the very end of rendered callback.
    Session.set('contentWindowRenderMark', '' +
        new Date().getTime() +
        Math.floor(Math.random() * 1000000) );
}


Template.renderNav.contentData = function() {
    // You don't have to actually use the mark value,
    // but you need to obtain it so that the dependency
    // is registered for this helper.
    var mark = Session.get('contentWindowRenderMark');

    // Get the data you need and prepare for displaying
    ...
}

With further information you've provided, we can create such code:

content.js

Content = {};
Content._dep = new Deps.Dependency;

contentWindow.js

Template.contentWidnow.rendered = function() {
    Content.headers = this.findAll(':header');
    Content._dep.changed();
}

renderNav.js

Template.renderNav.contentData = function() {
    Content._dep.depend();
    // use Content.headers here
    ...
}

Problem

I have a template helper called {{renderNav}} in a template Nav e.g. ``` Template.Nav.renderNav ``` and within that helper function I want to parse the rendered output of another helper within a different template For example the helper ``` Template.contentWindow.content ``` which provides the html for ``` {{content}} ``` and my renderNav helper wants to part the html that replaces {{content}} to generate the html for ``` {{renderNav}} ``` how would I do this? right now the {{renderNav}} helper executes for or runs more quickly and so it is unable to parse the html that replaces {{content}} @Hugo - I did the following in my code as you suggested ``` Template.contentWindow.rendered = function() { debugger; return Session.set('entryRendered', true); }; Template.Nav.renderNav = function() { debugger; var forceDependency; return forceDependency = Session.get('entryRendered'); }; ``` When I run it, the debugger first stops when executing the renderNav helper. (Which makes sense with what I am seeing in terms of the race condition). Then contentWindow renders and I hit the breakpoint above the Session.set('entryRendered', true). But then the renderNav doesn't run again as you suggest it should. Did I misinterpret or incorrectly implement your suggestion?

Original source