There are still conventions for loading model/table classes in the controller with the same name, but nothing for validators.
Right now validators are built in the table classes and applied to entity data during saving. While it is not required to put validations into a class that is an option people can use. How would a controller using a validator work? Wouldn't that make it harder to apply validation when one model alters the data of another? -mark -- Like Us on FaceBook https://www.facebook.com/CakePHP Find us on Twitter http://twitter.com/CakePHP --- You received this message because you are subscribed to the Google Groups "CakePHP" group. To unsubscribe from this group and stop receiving emails from it, send an email to cake-php+unsubscr...@googlegroups.com. To post to this group, send email to cake-php@googlegroups.com. Visit this group at http://groups.google.com/group/cake-php. For more options, visit https://groups.google.com/d/optout.
