-
-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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
[Validator] Incorrect documentation #6159
Comments
I can confirm the behaviour you described. The JSR 303 specs (which the Validator component implements) describes the documented behaviour: http://beanvalidation.org/1.0/spec/#d0e1425 So it seems like the code should be changed to reflect this. |
Actually, I misread the specs and the docs should be fixed instead:
So we should fix the docs instead. Can you maybe do that by clicking on the "edit" button of this particular page? (if you aren't sure or don't have time, feel free to say so and someone else will have a go on this). |
Thank you for response @wouterj, but I'm not sure that I fully understand what to do here. In my previous example, should the Also, I think that the B.III should be applied here:
So I do think that the documentation is correct and the code should be changed. /cc @webmozart |
Hmm, I think you're correct @aybbou. I think I confused "superclass" with "subclass". Can you please open an issue in the code repository? (or even fix it in the code?) |
@wouterj to me sounds good regarding the explanation about Sequence group in docs http://symfony.com/doc/current/book/validation.html#group-sequence nldr: if you set User as third argument, only validations from this class will be used. The best here is to not fill the third argument, isn't it? Mickaël |
I'm closing this because the conclusion was that docs are correct and this is a bug in the code. Thanks! |
Hi,
So I was looking at the documentation for validating objects, and I read here that :
But when I tested this, it wasn't working :
and
and then in the controller I do something like :
I have a
ConstraintViolationList
object containing only the$email
violation. So I was wondering if this is a bug in the Validator component or the documentation is not up to date.I am using Symfony 3.0.1 & PHP 5.6
Thanks.
The text was updated successfully, but these errors were encountered: