Fix resource limit scores resetting on include #1485
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
include
is used in a template, it'll go throughLiquid::Template#render
, which is called on a new template instance but with the same context. Meaning the "partial" that was included will keep using & updating the sameLiquid::ResourceLimits
instance. Among those updates though, there is an initial, unconditional reset of the scores done insideLiquid::Template#render
.After this fix, the reset will only be applied if the method was not called inside a partial context.