I'm curious as to what everyone's hate for @validate is. I have been a long time user of FormEncode and new to Pylons and found @validate pretty damn slick. I've got custom validators and chained validators and never really had a complaint. I've definitely ran into situations that have me scratching head as to how I am going to get it to work but there always seems to be a way and it ends up being reasonably elegant with FormEncode.
2009/10/23 Jonathan Vanasco <[email protected]> > > 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. > > > -- Never take life seriously. Nobody gets out alive anyway. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
