Daniel: There are already a few tickets for forms/valiation at: http://trac.symfony-project.org/report/24
If you haven't done so already, I suggest wrapping your head around how Validation (and the property path system) works, as it's definitely the more complicated component of the two. IMO, the Form component isn't too much different than Symfony 1.x (or if it is, it's easy to migrate to), but the object-level Validation is completely new (for Symfony/PHP at least, it's based on JSR-303). Regarding specific fields, I know CollectionField is on the todo list - it's the only thing in Forms that isn't working as-is for me, and we're using a custom version in the meantime (too many hacks inside to contribute upstream at the moment). Perhaps a great step might also be writing unit tests and correcting documentation where there may be gaps. Units tests would be good practice either way, as any fixes should come paired with a test to vouch for the corrected functionality :) Feel free to follow up with any questions (either here or directly). On Sep 13, 9:19 pm, "Daniel A.Tiecher" <[email protected]> wrote: > Hello everybody! > > I'm new to this list and got here after Fabien's post on the symfony > blog calling for contributors to complete Symfony 2. > > What got my interest was the Forms/Validation framework and I would > like to know which steps I need to take to at least try to help you > guys on this task. > > Cheers! -- 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
