-
Notifications
You must be signed in to change notification settings - Fork 41
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
Unexpected validation pass about nested fields #244
Comments
Full example is here: https://gist.github.com/mununki/1e9cecfcdf9d52b22aafd517b7b33df5 |
Hey @mununki, first off, sorry for the delay, it has been a busy month.
Actually, thank YOU for the awesome work on the compiler, I was just about to DM you on twitter to thank you (and all people from green-labs) for the amazing contributions to the ReScript ecosystem <3 About the issue, I'll try to run the given example in a demo project and I'll come with a solution as soon as possible. @fakenickels I think you can help us here, since you're worked on this part. |
Hey @mununki I created a demo project and ran your example locally. It's a weird behaviour, the reschema should validate the field state and looking for the nested error constructor instead of just returning a valid state. We're working on fix this and we'll release as soon as possible. Since this is not an issue with ReForm, I'm going to move the conversation to the ReSchema's repository, ok? You don't do need to do anything, I'll replicate the issue there and tag you to follow the incoming updates. |
@vmarcosp Thank you for following up on this issue.
No problem. 👍 |
Hi team!
Thank you for your awesome work! I think the ReForm is a unique form validation library built from the scratch with ReScript. I really like your work.
I encounter a weird unexpected validation pass about the nested field array. Here is my example:
The length of errors in
comment:1
is not 0, so it means that this predicate function returnsNestedErrors(errors)
. But none of the indexes in the nested field has an error. So, the submission proceeded even though the nested fields are not satisfied in the custom schema.I guess that
validate
function (https://github.com/rescriptbr/reschema/blob/master/src/ReSchema.res#L287:L292) in ReSchema should check theNestedErrors
there. Or anything I missed for the nested fields validation?The text was updated successfully, but these errors were encountered: