fix: prevent useMutators from using previous call arguments #296
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
Contributor
|
Preview is ready. |
Contributor
|
Playwright Test Component is ready. |
thebraid
force-pushed
the
fix/usemutators-no-previous-args
branch
from
a13f56e to
ef88c59
Compare
thebraid
force-pushed
the
fix/usemutators-no-previous-args
branch
from
ef88c59 to
53e22dc
Compare
bocembocem
approved these changes
Apr 28, 2025
thebraid
force-pushed
the
fix/usemutators-no-previous-args
branch
from
456a2e2 to
53e22dc
Compare
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.
When calling useMutators in a component that is used for two fields within the same form, changes to one field affect the other because the arguments passed to mutate are stored in internal state and are added to each subsequent call.
This problem is described in #291