On 03.11.2010, at 19:21, Benjamin Eberlei wrote: > Its just not feasible from a programmatic perspective. The validation > component is supposed to be decoupled from the form. You should be able > to validate your models without a form instance (think webservice, cli, > tasks, ...). > > So where would the validation then be if not on the value of the model > itself? If it would be in an array "again", then the whole concept of > the new form/validation framework would break into pieces. > > new paradigm: Its the object that is getting validated, with its values! > not the form. ;)
which makes exactly zero sense from a UX point of view. it also makes zero sense from a security point of view. if i acknowledge that there is a also a need to at times validate object state, but imho this is an edge case. and if its a significant enough edge case we should cover it. but you validate user input as soon as possible and without modification. also just look at the complexity it adds to have to handle any modification via lifecycle events: https://gist.github.com/661150 final point: if its independent of the form, then it should be also capable of being used inside the form! 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
