On Mon, Jan 11, 2010 at 7:07 PM, Chris <[email protected]> wrote: > FormEncode is great too, but also seems more complex. I often find > myself wondering if I'm sub-classing the right thing or overriding the > right methods in my custom validators. For example, when subclassing > FormValidator, you override .validate(), when subclassing > FancyValidator you do ._to_python(). But you can also have a > FancyValidator subclass act as a form validator if it is run in > chained_validators. There so many ways to do things, I'm just not > sure if I'm doing any of them right. Of course, my understanding of > FormEncode could be completely wrong!
I don't use FormValidator. I thought it was the validator for forms, but when I interviewed Ian he said it's for cases where you want to chain to another validator even if the form is partially invalid. I've never understood when that would be useful. I use Schema when it's convenient, and FancyValidator otherwise. -- 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 [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.
