close #8653 when useFormContext provide no generic for type check #8654
Conversation
This file contains 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
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 363e6ea:
|
|
Size Change: 0 B Total Size: 17.6 kB ℹ️ View Unchanged
|
bluebill1049
added a commit
that referenced
this pull request
Jul 9, 2022
bluebill1049
added a commit
that referenced
this pull request
Jul 10, 2022
bluebill1049
added a commit
that referenced
this pull request
Jul 10, 2022
bluebill1049
added a commit
that referenced
this pull request
Jul 13, 2022
* V8: feature: useFieldArray rules props (#8102) * useFieldArray rules prop * remove required prop * combine logic within validateField * remove logic * update unset method to support root node in array * update api extrator * update type * update useEffect validation logic * update api extrator * fix submit field array error * extract logic into its own function for update root error object * 8.0.0-alpha.3 * update with unit tests coverage for rules validate, minLength and maxLength * include support for required prop for consitent API and test coverage * update API * save some bytes * upgrade to react 18 * Revert "upgrade to react 18" This reverts commit d1c3bf7. * update react * fix cypress test * remove render count * udpate package and include test coverage for nested field array * fix unit and cypress tests * update lock file * revert package * avoid react native breaking change and fix test * fix test and type error * 🚔 close #8653 when useFormContext provide no generic for type check (#8654) * close #8653 when useFormContext provide no generic for type check * update api contract * 🛰 useFormContext include type tests (#8656) * Revert "🚔 close #8653 when useFormContext provide no generic for type check (#8654)" This reverts commit 2e0c3f8. * Revert "🛰 useFormContext include type tests (#8656)" This reverts commit 34af5b3. * 🥼 update changelog related to #8653 * 7.34.0-next.0 * check validation required for field array if not array or empty length * include unit tests coverage for validate fields for array fields * update api extrator
|
This is still blocking me I'm passing errors in as an object: This is leading me to get errors like: or |
|
I'm getting very similar error, @niemyjski did you manage to solve this? Or at least a workaround? |
|
No, I ended up pinned to an older version :( |
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.
ref: https://codesandbox.io/s/react-hook-form-chakra-ui-forked-0kcquv?file=/src/App.tsx
related: #8652 #8619
Prevent compile error when user not provide generic for context