On Wed, Apr 2, 2008 at 5:43 PM, Thomas Rabaix <[EMAIL PROTECTED]> wrote:
> I get that point but this behavior seems to force the user to write > validator for each specifics validators. To me, that's a great feature. It will force developers to think reusability and factorization :) Nonetheless, imagine how forms unit testing will be easy, from now. > So a form will depends on X externals validators which may not be used > somewhere else. > [...] > My feelings is that too many files or validators add more complexity, > and will not help to migrate to sf1.1 I guess on a standard project, you won't code many custom validators. And if you have too, I think they would always be better located in dedicated php classes, than in the isValid() method (or in yaml files, which are hard to debug and maintain - magic can be black voodoo somet^H^H^H often). > Otherwise the method isValid should be set as 'final' That would be a bit rude, as you may want to do a lot of other things by overriding this method... ++ -- Nicolas Perriault http://prendreuncafe.com/blog GSM: 06.60.92.08.67 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
