-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Using optionality and asynchronous rules in the same chain #206
Comments
This should actually be fairly easy, it would probably require either an additional rule ( Generally speaking this idea makes sense and should be implemented. Considering it's a new feature this one can be in 1.5.0. |
So @usernamus, I've created #223. Is that what you were looking for? |
Wow. Thank you. This really seems to be what I need. |
Alright, barring review we can target this for the next release (which will be 1.5.0). |
Just FYI @usernamus, the next release will still contain this feature but it will be slightly different than #223 had it. The asynchronous validation will simply be supported on the |
@barfurth oh, that sounds great. Thanks you so much |
I would like to be able to write something like this chain of validations:
v8n().optional(v8n().email().checkEmailAvailable())
email
– regular rule for email validation (pattern)checkEmailAvailable
– async ruleBut right now it's not possible because inside optional rule we use
.check
strategy.Is there a chance that this behavior can be implemented?
The text was updated successfully, but these errors were encountered: