Skip to content

Add range resource-limit regression specs - #165

Merged
ianks merged 4 commits into
mainfrom
ianks/range-resource-specs
Sep 16, 2026
Merged

ianks merged 4 commits into
mainfrom
ianks/range-resource-specs

Conversation

@ianks

@ianks ianks commented Sep 16, 2026 •

Copy link
Copy Markdown
Contributor

Adds shared regression coverage for the range resource accounting in Shopify/liquid#2117.

Nine output cases were captured from the Liquid tests using the existing ShopifyLiquidPatch importer. Ten bounded resource-limit cases cover empty and nonempty loops, cumulative partials, offsets, reversal, metadata, captures, and tablerow closing markup. Allocation guards, exact counter assertions, repeated-render state, and custom Range subclass behavior remain Ruby tests because the YAML format can't express those checks.

The resource cases use a staged range_resource_limits capability. Built-in v5.13 reference adapters and generated JSON-RPC adapters opt out. After this PR merges, Shopify/liquid#2117 will pin the merged liquid-spec revision and run the staged cases through its own adapters.

This also fixes Range capture so exclusive and endless endpoints survive YAML round trips. Inclusive ranges keep their existing two-item encoding.

In a clean v5.13 checkout, the pre-push gate passes and the reference adapter runs the nine imported cases while skipping the staged capability. A separate local run against Shopify/liquid#2117 passes all ten staged cases; the pre-fix Liquid baseline fails the four accounting regressions.

Depends on the CI baseline merged in #164.

Assisted-By: devx/b8d3b9bd-01a3-41b1-90f8-632318b798e4
Assisted-By: devx/b8d3b9bd-01a3-41b1-90f8-632318b798e4
@ianks
ianks requested a review from karreiro September 16, 2026 05:05
Assisted-By: devx/b8d3b9bd-01a3-41b1-90f8-632318b798e4
Assisted-By: devx/b8d3b9bd-01a3-41b1-90f8-632318b798e4
@ianks
ianks merged commit 84bf25e into main Sep 16, 2026
3 checks passed
@ianks
ianks deleted the ianks/range-resource-specs branch September 16, 2026 18:22
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