Cannot ignore curly braces in front matter string
See original GitHub issue---
title: "Join <raw>{{admin_name}}</raw>"
preheader: "Join @{{admin_name}} "
---
Expected behavior: The curly braces should be ignored. What happens: When the template is built the template replaces this variable with “undefined”
The above options do not work - this is inconsistent with what’s expected as a syntax in the template.
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Is it true that I can't use curly braces in Python? - Stack Overflow
I was reading that Python does all it's "code blocks" by indentation, rather than with curly braces. Is that right?
Read more >How to escape curly braces within \texttt{} - TeX
another technique that works is \textt{\char \{} (with a backtick between \char and the \{ , which can't easily be shown here in...
Read more >Double curly brace {{ }} conflict override - feature - HUGO
Even the ability to turn off template binding via the Front Matter would be a nice feature, I would just disable it for...
Read more >Template Designer Documentation - Jinja
It's important to know that the outer double-curly braces are not part of the variable, but the print statement. If you access variables...
Read more >GitLab Flavored Markdown (GLFM)
In GitLab, front matter is used only in Markdown files and wiki pages, not the other ... The wrapping tags can be either...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay that works! Yes - I needed to escape on the layout too, But works with a single @ applied to both places.
Just tested and it works fine, can you provide an example where it fails?
You can theoretically escape
{{{ content }}}
with@{{{ content }}}
, but it looks like it’s not working as expected inposthtml-expressions
. Got it working with{@{{ content }}}
(I know it’s weird but it’ll have to do until we get it fixed).<raw>{{{ content }}}</raw>
should also work.