Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
When using
mergeIfMissing()(or any method that internally callshas()orinput()before mutating request data), the local$this->inputcache gets populated and locked. Any subsequent merge into the underlyingInputBagis invisible toinput(),has(), and the__get()magic method because they all read from the stale cache.Minimal reproduction:
input()andhas()inRequestHelperlazily populate$this->inputon first access and never invalidate it:Fix
Invalidate
$this->inputcache insidemerge()so any subsequent read re-fetches fresh data from the underlyingInputBag:Also fixed
The targeted invalidation approach is the minimal, lowest-risk fix — it preserves the intended optimization while correcting the staleness bug.