One problem with @validate is the 'state' argument is useless unless you're passing data that's the same for every request -- in which case the data could be put in the validator itself and 'state' isn't needed. But some interesting validators depend on the current database record, or whether an attachment file exists in the filesystem, etc. This is only known after the action starts running and can look up other data based on the input. Or the validator has to do the lookups itself, which is bad encapsulation and what 'state' was designed for. So we need something equivalent to @validate but can be used inside the action. Does this refactoring allow this?
-- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to pylons-discuss@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
