-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Always need to set delimiters in custom render(text) function blocks #489
Comments
Looks like a bug to me. Need someone to confirm the behaviour, or send in a PR with a failing test. (or both the test and the fix) 😄 |
I updated my issue with some extra code. It might be that I just misunderstood something while writing the function but it seemed pretty straightforward on the Readme.md
|
Yep, I see the reason why this happens. It happen when using lambdas (like your case) and partials (I think), due to that section of the template being parsed again. Thanks for the additional info! |
I was able to get this issue into a workable test case:
I'm working on a fix for it now. |
I have a template code
And it outputs
<.&permalink.>
as <.&permalink.> - it doesn't change the variable to a value.Then I noticed if I write
{{permalink}}
instead, it changes the variable with the value assigned in the JS object.Then I tried setting the delimiter inside
<.#insert_image.>
block and it finally rendered with a value instead of the variable name.Sorry, I forgot to add my
render(text)
code. It might be that I just misunderstood and did something wrong.I'm using the 2.1.3 version. Is this normal behavior or is it a bug?
The text was updated successfully, but these errors were encountered: