-
-
Notifications
You must be signed in to change notification settings - Fork 159
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Yup v1 support #508
Comments
I don't think those breaking changes affect us. Could you try it out and let us know? |
I tried and ran into an issue regarding ObjectSchema type matching. type Resolver extends only Yup.AnyObjectSchema butI think it should be Yup.ObjectSchema or at least both. |
It appears that types are broken.
|
Upgrading to For a transition period, maybe a separate resolver for this new version could be added while marking the old one as deprecated somehow? |
Definitely breaking changes. There's no longer an exported |
Ola guys 👋🏻 Feel free to review :) |
Any estimate on when this change could be released? (I suppose it should be a major change, as it's a breaking change for |
We'll release a major with severals changes including for yup resolver. We're working on it with @bluebill1049 |
Was there a fix to the |
@ethanhoroschak Please open a new issue if it's yup resolver related. It seems to be related to Yup itself |
@jorisre My mistake! Found the open issue for Yup if anyone else stumbles on this thread for the same search query: jquense/yup#1954 |
Hi. For now react-hook-form/resolvers supports yup v0.32
But recently yup v1 was released.
It contain breaking changes jquense/yup#1906
Will be good to have support of yup v1 too
The text was updated successfully, but these errors were encountered: