Repository navigation
Conversation
commit: |
This branch has not been deployed
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.
Why
hook-use-stateasks for an unused setter when a client component deliberately keeps an initial query snapshot built from an unchanged Next App Router page input. Allow the supported nativeURLSearchParamsbuilder while retaining advice for other single-value state declarations.What changed
This is a bounded source proof using ordinary framework and declared dependency API boundaries. It does not interpret arbitrary dependency implementations or prove runtime heap purity. Stacked on #2200.
The review also closes two provider-refusal gaps: constructor access through destructuring in supporting source, and executable JSX script content. Those sources must prevent the initial-snapshot exemption.
Test plan
hook-use-statefuzzing: 500 iterations, seed 42; 2,246 executions, 400 target firings, no findings.This PR remains draft while the updated ancestor fixes are integrated and performance profiles and remote parity are completed. Local functional checks do not establish full-corpus parity or performance clearance.