EmptyDrop and Object indexing about liquid-rust HOT 7 OPEN

Its been a while since I've dug into the meaning of this on both sides but I think we were aiming for strict_variables and strict_filters exclusively

From https://github.com/Shopify/liquid

By default, the renderer doesn't raise or in any other way notify you if some variables or filters are missing, i.e. not passed to the render method. You can improve this situation by passing strict_variables: true and/or strict_filters: true options to the render method. When one of these options is set to true, all errors about undefined variables and undefined filters will be stored in errors array of a Liquid::Template instance. Here are some examples:

from liquid-rust.

I think that's a fair goal for values leaving a filter chain, but it seems like the inconsistent behaviour between the two cases above is surprising. I'm trying to figure out if there's even a way to handle this case in the template, because as far as I can tell there's no way to check if some value is set without getting this error

from liquid-rust.

it seems like the inconsistent behaviour between the two cases above is surprisin

Yes, I had missed the inconsistency in my first read through. Thats something that needs looking into.

I'm trying to figure out if there's even a way to handle this case in the template, because as far as I can tell there's no way to check if some value is set without getting this error

You can do {% if value %} (test) or `{% data contains "value" %} (test).

from liquid-rust.

Thanks, if you have any inclinations on where I can poke at this issue in the codebase I'd be happy to see if I can resolve the inconsistency

from liquid-rust.

Any thoughts or follow-up on this one?

from liquid-rust.

The question for any of this is what does Ruby's implementation do with those strict flags set. Any discussion or PR should be focused on that.

from liquid-rust.

Okay, I've done a repl test against the latest ruby gem and found that filters are not allowed to start with undefined variables when strict_variables is set - which means the former case is incorrect for this implementation, ie {% assign var = value | default: 42 %} does not currently error, but should

from liquid-rust.