You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful to pass liquid to filter implementation, to allow parsing and rendering filtered object.
Use case:
A translate filter 't' takes a template string like "hello {name}" and a name arg, when current implementation, it not possible parse the string with the given scope.
The text was updated successfully, but these errors were encountered:
It's easy to add liquid to this, but it maybe not as useful as you think. Since the {% raw %} tag is the only way to escape in Liquid, the following template is invalid:
{{ "hello {{name}}" | render:"foo" }} // {{ foo }}s are not allowed to be nested
I'll expose the liquid instance to filters anyway.
Hello,
It would be very useful to pass liquid to filter implementation, to allow parsing and rendering filtered object.
Use case:
A translate filter 't' takes a template string like "hello {name}" and a name arg, when current implementation, it not possible parse the string with the given scope.
The text was updated successfully, but these errors were encountered: