> That solves another problem we have: how to trigger a form error in > the action after the validator has passed.
exactly. that's been my motivation. > Normally you don't want to decorators in non-decorator situations, so > you'd need another function for this. yeah... i might take a stab at that tonight. the pylons team did all this great work on form validtation - it's almost silly that its hardcoded into a decorator to access it. it's awesome that pylons will validate my form via a decorator, but sometimes i just want to know if the form is valid or not, without the decorators. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
