Clarify structure of nested errors in a custom resolver #1160
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
The existing documentation infers that the return value of the `errors` key on a custom resolver should use flat keys that match the path of the error (since this is the convention throughout the lib), however it turns out that the internal code for RHF actually expects a hierarchy to be returned... kept me up till 3am last night tracking this one down 😅 - RHF is awesome!
✅ Deploy Preview for sage-cassata-31d224 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
bluebill1049
approved these changes
Jul 15, 2025
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.
The existing documentation infers that the return value of the
errorskey on a custom resolver should use flat keys that match the path of the error (since this is the convention throughout the lib), however it turns out that the internal code for RHF actually expects a hierarchy to be returned... kept me up till 3am last night tracking this one down 😅 - RHF is awesome!