On Jan 30, 2007, at 4:19 PM, Christopher Arndt wrote:
> > Jorge Godoy schrieb: >> "Ed Singleton" <[EMAIL PROTECTED]> writes: >> >>> You need to have some options in your options so that it can guess >>> what validator to use. > > Wow, that's a crappy API! I'll have to agree with you ;) http://tinyurl.com/3xwsa7 http://tinyurl.com/2tzvu2 The best way to fix it is to define a validator explicitly in the field, not in the schema. That guessing behavior is there in order to keep backwards compatibility, fortunately I've removed it from twForms in which you need to explicitly define a validator for each field that needs one. An exception being repeated fields in which a ForEach validator is built (if none given) using the individual field's one, same for multiple select fields; and forms, which create (or extend an existing one) with the children's validators. Alberto --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
