Agreed with Mike about the shortcomings with @validate. There's a lot of things I don't like about it.
Chained Validators are not an option for me, and likely others. They work great for validating the input, but in many cases you have business logic within the controller that can then invalidate the process. It's sad that in Pylons the options are only to put controller logic in a validator, or devise some way to otherwise emulate a form error. I may just write my own @validate routine , and tie it to helper functions that can be called independently to handle populating the errors and displaying them. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
