Forums

Some of the variables I use in my Handlebars templates are global. They tend to be ones I store in YUI_config / Y.config
What I do is that I set this object as part of the model passed to the Handlebars template. Not very elegant.



I have a few questions about this:

1. Whenever I am in the context of a helper, I lose access to the model elements passed to the template. The helper only "knows" the variables passed to it through the helper interface. This does not happen in my Java implementation of Handlebars and it doesn't make sense to me either. I'm not sure which is right and what is the suggested way for dealing with global variables.

2. Is there perhaps a way to global variables at a central level so that they will always be included as part of the data-model?

Kind regards,
Marc

So, according to the Handlebars.js documentation, you should be able to access the parent scope (which seems to suggest the root template scope) from withing a Partial or Helper by using {{../myVar}}.

When I try this I get an error because depth1 is undefined. So, it seems that the ../myVar is parsed correctly to look up a scope one level up. But that level is empty.

Any suggestions here?

Kind regards,
Marc

Yes, I think that is what I'm saying.

I'll give you an example





I don't see the undefined depth1 error anymore. Could be the 3.6.0pr4->3.6.0 upgrade. But yes, I don't have access to the original context when I use the Path ../YUI_config.serverUrl within a registered partial template.

Based on the Handlebars.js Path docs I think you should be able to. If not, than it would be useful to be able to register a mixin object when you register a partial to be able to expose some global variables.