Closed Hunter-Gong-Attentive closed 4 months ago
Will work on this. Thanks!
Was looking into this and I think the solution may be as simple as this here https://github.com/bkiers/Liqp/pull/305
@Hunter-Gong-Attentive nice work! Merged and new version 0.9.0.3
released with it (requires some time to became publicly available)
Hello, I am currently running version
0.8.3.3
of this library in my application and when going to upgrade to the more recent0.9.0.2
that some of our previous logic is now invalid due to these type checks. This appears to be happening even when thewithStrictTypedExpressions
flag is set to false, and based on the README description of this option, this appears to be a bug.Steps to reproduce:
When rendering a comparison between a number and a string and
withStrictTypedExpressions
is set to falseExpected Behavior: An empty string should be rendered Actual Behavior: RuntimeException is thrown
Flag usage elsewhere
This behavior appears to be inconsistent and does not apply to comparison which contain booleans or make non-relative comparisons. It is unclear why these would be intentionally allowed, but the above would not.
IE, these examples both render fine.