On 07.10.2010 17:26, Bernhard Schussek wrote:
> Should we then maybe rename the Validation constraint to Set? (or
> something the like)
>
> Then it would more logically explain its usage.
>
> /**
> * @validation:NotNull
> * @validation:Set({
> * @validation:DateTime,
> * @validation:DateTime
> * })
> */
I agree this makes more sense, and sorry if the following is already
implemented, I haven't checked, but is it possible to have
@validation:Or/And logical ops? I don't think they make sense in too
many cases, but when you need it it's gonna be painful if you have to
write a custom validator just for that purpose.
Cheers
--
Jordi Boggiano
@seldaek :: http://seld.be/
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to symfony-devs@googlegroups.com
To unsubscribe from this group, send email to
symfony-devs+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
