Awesome detective work, Jeremy, thanks - glad I wasn't just going crazy. :)
I suppose the quickest fix is just to change the UPDATE document to cross out the @assert change until PR10. It's possible that a lot of people have changed their validation models to @assert and simply haven't noticed that their models and forms always validate now, even with incorrect data! That's a little worrying, although I don't really know what to do about it. I guess you can't block unrecognised annotation namespaces, because you want to allow for other docblock usages (like… documentation ;) On 30 Mar 2011, at 20:32, Jeremy Mikola wrote: > It appears that the "@validation" prefix is still set in the symfony/symfony > master branch. > > When FrameworkExtension enables validation annotations[1], it merges a > provided array (if any) atop the "validator.annotations.namespaces" DI > parameter. According to validator.xml, the parameter is still defined with > the "validation" prefix[2], even in the PR9-tagged version[3]. > > [1] > https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/DependencyInjection/FrameworkExtension.php#L496 > [2] > https://github.com/symfony/symfony/blob/master/src/Symfony/Bundle/FrameworkBundle/Resources/config/validator.xml > [3] > https://github.com/symfony/symfony/blob/vPR9/src/Symfony/Bundle/FrameworkBundle/Resources/config/validator.xml -- 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
