> So from the POV of the form instance, a validation error on a property that > isnt associated to a field just makes the isValid() return false, but it has > no reference of this validation error anywhere?
No, they are (should be) attached to the first field found when traversing the property path upwards. This usually will be the form, i.e. the error will be a "global" error. Your feature request absolutely makes sense. I have added it to my TODO list. Bernhard -- Software Architect & Engineer Blog: http://webmozarts.com Twitter: http://twitter.com/webmozart 2011/1/18 Lukas Kahwe Smith <[email protected]>: > > On 18.01.2011, at 15:05, Bernhard Schussek wrote: > >> Hi Lukas, >> >> Currently this is not possible. > > > So from the POV of the form instance, a validation error on a property that > isnt associated to a field just makes the isValid() return false, but it has > no reference of this validation error anywhere? > > Maybe validation errors that are not attached to a property or the class > should at least be available via some method in the template? > > 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 > -- 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
