Access a variable outside the scope of a Handlebars.js each loop
I have a handlebars.js template, just like this:
{{externalValue}}
<select name="test">
{{#each myCollection}}
<option value="{{id}}">{{title}} {{externalValue}}</option>
{{/each}}
</select>
And this is the generated output:
myExternalValue
<select name="test">
<option value="1">First element </option>
<option value="2">Second element </option>
<option value="3">Third element </option>
</select>
As expected, I can access the id and title fields of every element of myCollection to generate my select. And outside the select, my externalValue variable is correctly printed ("myExternalValue").
Unfortunately, in options' texts, externalValue value is never printed out.
My question is: how can I access a variable outside the scope of the handlebars.js each from within the loop?
Try
<option value="{{id}}">{{title}} {{../externalValue}}</option>
The ../ path segment references the parent template scope that should be what you want.
Or you can use absolute path like this:
<option value="{{id}}">{{title}} {{@root.user.path.to.externalValue}}</option>
I saw many links with 404 for documentation about this topic.
I update it with this one, it is working in April 1st 2020:
https://handlebarsjs.com/guide/expressions.html#path-expressions
Some helpers like #with and #each allow you to dive into nested objects. When you include ../ segments into your path, Handlebars will change back into the parent context.
{{#each people}}
{{../prefix}} {{firstname}}
{{/each}}
Even though the name is printed while in the context of a comment, it can still go back to the main context (the root-object) to retrieve the prefix.
WARNING
The exact value that ../ will resolve to varies based on the helper that is calling the block. Using ../ is only necessary when context changes. Children of helpers such as {{#each}} would require the use of ../ while children of helpers such as {{#if}} do not.
{{permalink}}
{{#each comments}}
{{../permalink}}
{{#if title}}
{{../permalink}}
{{/if}}
{{/each}}
In this example all of the above reference the same prefix value even though they are located within different blocks. This behavior is new as of Handlebars 4, the release notes discuss the prior behavior as well as the migration plan.
Follow WeChat
Success story sharing
Want to stay one step ahead of the latest teleworks?
Subscribe Now相似问题
- How do you access the matched groups in a JavaScript regular expression?
- What is the scope of variables in JavaScript?
- How to loop through a plain JavaScript object with the objects as members
- Dynamically access object property using variable
- Is there a reason for C#'s reuse of the variable in a foreach?
- What are the nuances of scope prototypal / prototypical inheritance in AngularJS?
- Why does my JavaScript code receive a "No 'Access-Control-Allow-Origin' header is present on the requested resource" error, while Postman does not?
- How to access the correct `this` inside a callback
../repeatedly depending on how many scopes away from the value you are.