-
-
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
missed filter not throwing parse error #271
Comments
There is a strictFilters option available, here's a demo: https://jsfiddle.net/kxetzqh5/ |
Hey, thank you for the quick response. Here added a demo: https://jsfiddle.net/sarbajit/hrxmsedp/7/ In the second h3 tag the parsing fails in Liqp. |
Thank you for clarification. If I understand correctly, it's about how to handle invalid filter syntax. The content of the second h3 in the jsfiddle above is: {{ age | default: 'now' date: '%d'}} // missing `|` before `date`
It's indeed invalid syntax, so I'm considering throw an ParseError maybe something like |
# [9.36.0](v9.35.2...v9.36.0) (2022-03-05) ### Features * Access array item by negative index, closes [#486](#486) ([049685b](049685b)) * allow strip filter with specified char, closes [#390](#390) ([c503cb2](c503cb2)) * appropriate error for malformed filters, fixes [#271](#271) ([01014ed](01014ed))
🎉 This issue has been resolved in version 9.36.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hii !
Facing an issue can you help me out.
Running
{{ data_due_date | default:'Nov 30' date:'%b %d' }}
template on liqp throws parse error.Exception in thread "main" liqp.exceptions.LiquidException: parser error "extraneous input 'date' expecting {OutEnd, '|'}" on line 1, index 36
.But running the same template with liquidjs engine throws no parse error. Is this a bug?
Thank you.
The text was updated successfully, but these errors were encountered: