fix: correct type for initialValues in FormProps interface #179
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
🦋 Changeset detectedLatest commit: 39b4b78 The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
In my testing, seems to working! 😄 Excellent work 🚀 |
|
Cool, I will merge it then. Thanks for checking it out. |
logaretm
added a commit
that referenced
this pull request
May 21, 2025
* fix: correct type for initialValues in FormProps interface * chore: add changeset * chore: formatting * chore: add playground * fix: added returntypes explicitly and overloaded useForm --------- Co-authored-by: Eugen Istoc <eugenistoc@gmail.com>
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.
Builds on top of the work done in #176 to address both cases.
In this PR we use function overloading for
useFormto steer it towards inferring the values from theschemaor theinitialValuesdepending on whichever is present or if both are, with preference to theschema.