rtyler
/
brokenco.de
1
0
Fork 0
Code Pull Requests Releases Activity

Jekyll loves to think everything is a liquid template 

Bug report from @jorgenpt
This commit is contained in:
R Tyler Croy 2021-08-01 10:25:33 -07:00
parent fe2f93a0be
commit 2921288e4e
No known key found for this signature in database
GPG Key ID: E5C92681BEF6CEA2
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
_posts/2021-07-05-accessing-variables-in-handlebars-rust.md
View File

@ -15,7 +15,7 @@ resolution. Unfortunately, the syntax can be quite unintuitive for accessing out
scope once in those nested scopes.
Handlebars is a largely declarative templating syntax which uses curlybraces
such as `{{var}}` for variable and helper substitution. The `#each` helper is
such as `{%raw%}{{var}}{%endraw%}` for variable and helper substitution. The `#each` helper is
important for loops, imagine the following data structure:
```json
@ -42,7 +42,11 @@ This could be rendered into a list on a page via:
</ul>
```
Inside the `#each` block the values of the indexed object become the scope for variable resolution, such that `{{name}}` actually refers to `data.repos[i].name`. This presents problems when the template must refer to outer scope variables, such as `mood`. In the Rust implementation this variable resolution can be accomplished through a path traversal style syntax such as:
Inside the `#each` block the values of the indexed object become the scope for
variable resolution, such that `{%raw%}{{name}}{%endraw%}` actually refers to
`data.repos[i].name`. This presents problems when the template must refer to
outer scope variables, such as `mood`. In the Rust implementation this variable
resolution can be accomplished through a path traversal style syntax such as:
```html
<ul>{% raw %}