-
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
Many constraints validation per fields #24
Comments
Hello, I belive you are correct, however the first error stops the check now as defined here Also, what you want here seems to be the html5 |
(Which is handled in Formidable) |
Hi @Gregwar, I'm using html5 I'm using Zend_Form and desire and work in migration to Formidable. But this is a big problem for me because my forms has many validators(in Zend_Form)/constraints. |
Ok, we should do some changes in the code to handle that, let's keep this
open until
Le lun. 13 mars 2017 22:15, Silas Ribas Martins <[email protected]>
a écrit :
… Hi @Gregwar <https://github.com/Gregwar>,
I'm using html5 number field yes, but I desire to have many constraints
and return many errors messages.
I'm using Zend_Form and desire and work in migration to Formidable. But
this is a big problem for me because my forms has many validators(in
Zend_Form)/constraints.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAWZrpemw448Cqj2j4B9HlCnwSKRRUgmks5rlbHngaJpZM4Mbyv7>
.
|
Many thanks! |
Hi @Gregwar, Any change? Thk's |
Actually I think that this is harder than it looks |
Maybe that should be an option, like retrieving all the errors or the first one of every field |
@silasrm Is this issue still relevant or can it be closed? |
Hi @Gregwar,
I've a case with 2 constraints but only 1 is returned in check:
Dump of
getFields()
:Dump of errors:
In my view, there should be 2 errors because a empty value "" is catched in both constraints.
Any error in my logic?
The text was updated successfully, but these errors were encountered: