fix: correct input.value type for useField and Field #947
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 b9570ec:
|
|
Published in |
jamesricky
added a commit
to vivid-planet/comet
that referenced
this pull request
Feb 24, 2022
This was changed in final-form/react-final-form#947
jamesricky
added a commit
to vivid-planet/comet
that referenced
this pull request
Mar 8, 2022
This was changed in final-form/react-final-form#947
kaufmo
pushed a commit
to vivid-planet/comet
that referenced
this pull request
Mar 30, 2022
This was changed in final-form/react-final-form#947
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 typing, when using strong lint rules
Closes #946