On 19.01.2011, at 12:44, Lukas Kahwe Smith wrote: > > On 19.01.2011, at 12:40, Bernhard Schussek wrote: > >> Shouldn't these be two different validators? That'd be less magic. >> >> I'm thinking about explicitely disallowing validators to be used both >> for classes and properties by introducing new classes ClassConstraint >> and PropertyConstraint. Then it'd be easier to check for errors (Max >> is not allowed to be put on classes, for instance). >> >> What do you think about this? > > Well it means more code to maintain on our side. But sure it would make the > code simpler.
BTW: I guess once we have a way to attach validation errors to form fields we probably wouldnt need the property validator for our use case anymore anyway. regards, Lukas Kahwe Smith [email protected] -- 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 [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
