fix(trigger): keep registered nested errors when trigger targets their parent - #13732
Merged
bluebill1049 merged 1 commit intoSep 11, 2026
Conversation
…r parent
Only skip setting a parent error container when no registered field
exists beneath it, so trigger('address') still surfaces
address.street errors instead of wiping them.
bluebill1049
approved these changes
Sep 11, 2026
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
2 participants
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.
Triggering a parent name (e.g. trigger('address')) with a resolver wiped that whole error subtree from form state, even when nested fields like address.street were registered and invalid. Trigger returned false while errors showed nothing, so no message could render.
This keeps the previous orphan-container fix intact: the parent container is only skipped when no registered field exists beneath it.