Meteor: Included templates still use the context of the parent

[bminer]

When you include a template using include "foo.blade" the subtemplate uses the data context of the current template.

[VanCoding]

Thanks for creating the issue. I'm so glad you're working on it!

Great work! :)

[bminer]

@VanCoding - has this been fixed? Can you confirm? Thanks!

[bminer]

Can someone please confirm that this bug has been fixed? Thanks!

[bminer]

This issue has been fixed. Included templates inherit their parent's locals and view helpers, but they can be overwritten. Issue #141 discusses the possibility of preventing included views from inheriting their parent's locals by default.

[brianephraim]

I'm having the following issue:

Within the file parent.blade, there is the following dynamic include:

include dynamicTemplateVaraible exposing someDataVariable

Here, someVariable is not available within the template we assigned to dynamicTemplateVaraible. Instead,
dynamicTemplateVaraible has the same locals as parent.blade.

-=-=-=-==-

However, in non-dynamic includes things behave as expected, as in:

include "nonDynamic.blade" exposing someDataVariable

Here, someDataVariable is available to the included template, and the parent locals are not available to the child.

=======
UPDATE

I found a pretty clean workaround.

Create a dynamicInclude.blade file.
That file should contain only this:
include dynamicIncludeName

Then when you want to use a dynamic include in a parent template, write it like this:
-var dynamicIncludeName = variableDerivedFromLocalOrWhatever;
include 'dynamicInclude' exposing dynamicIncludeName, whateverOtherVariable, anotherVariableEtc

What happens is dynamicInclude.blade will receive the exposed variables and use them as locals, as in this part, it is a static include and static includes do fine with receiving exposed variables. dynamicInclude.blade uses the variable dynamicIncludeName to dynamically include the desired dynamic template. Because this is a dynamic include, exposing variables doesn't work, and it receives the local variables of its parent, and those local variables (whateverOtherVariable,anotherVariableEtc) are the ones we intended to reach the desired dynamic template.

[bminer]

That's some weird behavior... I'll have to track down the issue as time permits. Thanks for the bug report!

[brianephraim]

Looks like my workaround doesn't work in Safari. I'm getting a nasty error:

TypeError: setting a property that has only a getter
at /Users/username/meteortest/groop3/views/characterList.blade:2:1

1 | -var dynamicIncludeName = nestedViewItem.includeName + 'Panel';
2 > include dynamicIncludeName

[bminer]

Could you post the full stack trace, please?

[bminer]

@defualt - I cannot replicate your bug. I believe that this issue is now closed. Try upgrading to the latest version of Blade and Meteor 0.6.2.