Fix inputs with disabled={false} throw an error (workaround)
#9313
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
djhi
approved these changes
Sep 25, 2023
fzaninotto
approved these changes
Sep 26, 2023
|
TypeScript complains |
djhi
approved these changes
Sep 26, 2023
|
I'm curious to know when this will be released. How often do we have releases? |
|
We usually release patch version every week. This one is scheduled for today |
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.
Fix #9261
Actually this is a workaround, since the root issue has to be fixed on RHF's side (react-hook-form/react-hook-form#10907)
Cannot be tested automatically.
To test:
disabled={false}somewhere in the demo