-
-
Notifications
You must be signed in to change notification settings - Fork 237
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
Support function calls #222
Comments
Sounds reasonable. I prefer the |
Do you mean check if the property is a function and invoke it automatically? I like that! Wouldn't that leave out all the functions that need parameters out though? |
I'm not sure if that's the behavior for shopify/liquid, but we definitely should align to that behavior whenever possible. I'll dig into it later, and any kind of PR is welcome. |
# [9.23.0](v9.22.1...v9.23.0) (2021-02-12) ### Bug Fixes * respect `fs` in parser options, for [#233](#233) ([4e82da6](4e82da6)) ### Features * support filters in if/unless/case, see [#287](#287) ([2f059f6](2f059f6)) * support function calls, closes [#222](#222) ([e37824f](e37824f)) * support layout none, closes [#299](#299) ([81e11bb](81e11bb))
🎉 This issue has been resolved in version 9.23.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hello,
I was wondering if there was plan for supporting function calls inside the templates.
{{obj.property()}}
breaks withunexpected token at "()"
. Can be worked around with anapply
filter{{obj.property | apply}}
but it's not really straightforwardassign
breaks with the same errorif
,for
andcase
don't break but seem to ignore the returned valueThat would be ideal to avoid too much gymnastics (and I guess allow what's already possible in Ruby, as function calls don't necessarily need parenthesis, or does Liquid break that behaviour?)
Cheers :)
The text was updated successfully, but these errors were encountered: