Replies: 2 comments
|
I think this comes down to Shopify/liquid's two distinct array/object stringifying methods/functions vs LiquidJS's one. Shopify has Then there's Given this template: {{ "1,2,3,4" | split: "," }}
{{ "1,2,3,4" | split: "," | strip }}Expected output: LiquidJS output: If you're going for maximum compatibility with Shopify/liquid, I'd call this a bug. If you're going for language consistency, I'd leave it as is and direct people to |
|
I guess, either way the the:
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I was trying the example jg-rp/liquid#194 and though the issue was my code not correctly rendering. Turns out the playground was deceiving me into thinking I had the correct behaviour.
It seems like the template library is consistent on the Python and library for the query:
While this library requires:
to return the correct result (from the Ruby library).
I have tried looking into the issues and also https://liquidjs.com/tutorials/differences.html, but could not find anything related.
Is this an actual issue, or is it meant to be like that?
And if I want to have consistent behaviour, can I ensure maximum compatibility to the spec somehow?
All reactions