Repository navigation
fix(useFieldArray): do not mark form dirty when array default is null - #13750
Merged
bluebill1049 merged 2 commits intoSep 17, 2026
Merged
bluebill1049 merged 2 commits into
bluebill1049 merged 2 commits into
Conversation
bluebill1049
approved these changes
Sep 17, 2026
Contributor
Author
|
Thanks for the review and merge. |
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.
Mounting useFieldArray over an array field whose default is null marked the form dirty immediately, so API-fed forms showed unsaved-changes state on load with zero user input. The mount guard now only initializes when the value is actually undefined.
Verified: new regression test fails before and passes after, field-array neighbors green.
Fixes #13749