liquid-rust
liquid-rust copied to clipboard
Liquid templating for Rust
Example test case: ```rust assert_template_result!("", wrap(" {% comment %} whatever {% endcomment %} "),); ``` This seems strange. We need to dig in further to understand under what situations the...
So this is a pretty large change I think, but as far as I understand the original Liquid HTML escapes everything that goes into filters by default, or something. Someone...
Currently, partial-templates can be named. This will be helpful for error messages. We should allow this for regular templates.
Example test: ```rust assert_template_result!("9", "{%decrement port %}", v!({ "port": 10 })); ```
Depends on #275 In addition to passing variables to #310, there is a special case of passing a single variable. There are two forms - `{% include foo.html with bar...
Right now, the parser generates `Box`s which are nested inside each other. - Can't really gain much from CPU caches - Heap fragmentation from all of these What if we...
Depends on #309 Jekyll seems to scope the variables to the partial's name and uses `=` for assignment - https://jekyllrb.com/docs/includes/#passing-parameters-to-includes This is in contrast to #310 for stdlib's include
Depends on #309 In looking at the Jekyll docs, it appears shopify allows expressions for include. https://jekyllrb.com/docs/includes/ Besides the parser (see #138), we'd have a problem with this because we...
Shopify says so > Note that you don't need to write the file's .liquid extension. https://help.shopify.com/themes/liquid/tags/theme-tags#include Jekyll says nothing https://jekyllrb.com/docs/includes/#passing-parameters-to-includes
Expanding on #232, we can capture the line associated with a block / filter / etc and report that during the render phase.