My personal opinion is that not everything what is possible is also automatically right. I understand benefits of error messages in model, but those benefits are gone just in moment you will (for example):
--- let anyone else touch your code - you can be sure they will modify messages in your models instead of adding 'error' => 'Custom message' to your inputs/errTags (or turning 'error' => true to 'error' => 'Custom message'. And I don't know how you, but I don't want anyone touch my validation rules in model ;) --- want to turn your app to multilanguage one. So you will modify your model's code, or implement some model's behavior, or customize some helper, or anything from above WITH i18n of custom messages... ...or anything else just because of wrong decision, which seemed like smart way ;) I hope you see at least one point now. From my point of view: you may say anything you want, but validation of data and error messages for humans are related, but they doesn't belong to same place. It is user who cares about stupid-proof text messages what goes wrong. With your philosophy - I am sure that you will surely end with tootip messages in model also, after your app will grow or be used by non-techs... IMHO fact that mariano is not doing it in examples of multiple validation rules in his article at bakery is for a reason. Just my 2 cents. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
