Refine Field Component Typing
#3896
Conversation
This commit enhances the typing within the Field component, rectifying a prior issue that had resulted in all props being implicitly assigned the type of any.
🦋 Changeset detectedLatest commit: bc0948a 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 |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
|
@jaredpalmer @probablyup is this something we can get out? this fix makes working with the |
|
There are some issues with this, namely that custom props which are required by a custom component cannot be passed to Field because the props type to field doesnt include the props from the custom component. We will need another generic for this or change the structure. I will take a crack at this, but I have to discuss it in a new issue so Jared gives a thumbs up before I spend a lot of time on it. |
This PR enhances the typing within the
Fieldcomponent, resolving a prior issue where all props were implicitly assigned the type ofany. A minor change set has been introduced because consumers of theFieldcomponent were previously able to (incorrectly) pass in any prop of any type. With this fix, some dependent TypeScript projects may need to refactor their code to provide the correct values for the compiler to avoid errors. If this doesn't necessitate a minor change set, I can adjust it to a patch accordingly.