v3.11.0-rc300.1 does not work with Blaze 3.0.0

[jankapunkt]

When using this packag with the rc 3.11.0-rc300.1 and Blaze 3.0.0 I get multiple issues when doing templating with regions:

• this.render is not available in whileWaiting
• {{> yield}} is not found
• this.render in action is defined but does not render anything

Reverting to 3.9.0 (which was used before we started migrating) works without issues.

[jankapunkt]

This also affects the creation of new projects using the --full option

[distalx]

I have encountered a similar issue where the this.render function is not passing data correctly when both the origin and destination templates are the same.

For example, the following calls do not pass any data when navigating from one route to another:

this.render("layout", "org_role_check", { target_template: "settings" });
this.render("layout", "org_role_check", { target_template: "members" });
this.render("layout", "org_role_check", { target_template: "calendar" });

Current Workaround:
To work around this issue, I have duplicated the org_role_check template and used it in the following manner:

this.render("layout", "org_role_check", { target_template: "settings" });
this.render("layout", "org_role_check_01", { target_template: "members" });
this.render("layout", "org_role_check_02", { target_template: "calendar" });

My assumption is that when the origin and destination routes share the same template name, data is not being passed or stored in the router queue.

[dr-dimitru]

@distalx it was the issue for long time, current workaround is:

{
  conf: {
    forceReRender: true
  }
}

It was introduced in v3.7.1 and has its own section in the Templating docs, have you tried it?

[dr-dimitru]

@jankapunkt @distalx is this issue still a case?

[dr-dimitru]

@jankapunkt @distalx check latest v3.12.1, let me know if it works well and if forceReRender: true solved your issues