Replies: 1 comment
|
@bdezso Did you ever find the reason for this? I've just been burnt by it.... It does not make sense |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Can someone explain why the onChange method expects an any parameter? The entire library works quite well with Zod, so we have strict types almost everywhere, except for the field.onChange function. What is the reason for this? Why did they decide to implement it this way?
All reactions