Assign TFieldsValues to fieldsValues instead of transformedValues #47
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.
Resolves #39
Support for the
TransformedValues
type was raised in issue #34. The example in that issue showed that when using Zod together with @hookform/resolvers/zod, there is no type support when the input and output differ.This was addressed in commit fc6c0a4 by passing
TransformedValues
to the generic ofuseLens
instead of the control’sFieldValues
. However, a lens only deals with the input side of the form and does not concern itself with the submission type after resolution, so this change is inappropriate.Suppose we have a Zod schema like the following.
In this case, the form’s input type is
FormInput
, and the submitted data type should beFormOutput
.