Skip to content

Add to_liquid_call_count feature for liquification-count specs - #163

Open
ianks wants to merge 1 commit into
mainfrom
ianks/to-liquid-call-count-feature
Open

Add to_liquid_call_count feature for liquification-count specs#163
ianks wants to merge 1 commit into
mainfrom
ianks/to-liquid-call-count-feature

Conversation

@ianks

@ianks ianks commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

StandardFilterTest#test_default_43dbbb97 asserts that to_liquid is called exactly twice for {{ a0 | default }} (Ruby liquifies once in find_variable and again in filter invoke). Engines that liquify once — or that lower default to bytecode instead of a real filter invocation (liquid-vm does this) — observe a different counter value while rendering identical output for ordinary values.

This adds a to_liquid_call_count feature (catalog: recommendation unnecessary, same spirit as ruby_drops) and tags that one spec with it, so engines can declare it as a missing feature instead of carrying the spec in known-failure baselines forever.

Downstream: lets Shopify/liquid-vm drop test/known_failures.txt to zero entries and drive test/rust_parser_known_failures.txt to 0 (liquid-vm PR to follow).

StandardFilterTest#test_default_43dbbb97 asserts that to_liquid is called
exactly twice for '{{ a0 | default }}' (Ruby liquifies in find_variable and
again in filter invoke). Engines that liquify once, or that lower 'default'
to bytecode instead of a real filter invocation (e.g. liquid-vm), observe a
different count while rendering identical output for ordinary values.

Tag the spec with a dedicated feature so such engines can declare it as a
missing feature instead of carrying it in known-failure baselines.

Assisted-By: devx/717e5259-915f-4a7b-af07-6abe46da5b90
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant