-
Notifications
You must be signed in to change notification settings - Fork 20
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
Nested composed validators do not curry as expected. #54
Comments
Hey, @jaridmargolin. Sorry for the misunderstanding. I originally wrote I'm swamped at the moment, so I may not be able to hop on fixing this immediately. You're welcome to open a PR if you like, though. Just let me know. Thanks! |
I was poking around in the source code but it wasn't immediately clear to me where / what the patch would look like. If I have some more time to dig into a fix, I will. Thanks for the quick response. |
Nested composed validators do not curry as expected.
* This may just be a misunderstanding of the lib is intended to work.
Expected:
isRerquired
works as expected and allows the field to propagate through.isName
however always returns a function. I can fix the issue by doing something like:but it seems as though the composed validator should work exactly the same as a created validator.
The text was updated successfully, but these errors were encountered: