Max Ischenko wrote: > > I was thinking about it myself. > > Haven't added because widget can't tell whether this field is required > or not and thus cannot init validator properly (I refer to not_empty > param). > > May be we should add a 'required' parameter to widget/formfield so that > a reasonable validator can be set? > > Good/bogus idea?
I think we can safely add a default validator that works with not_empty = False (like I'm going to do with the SelectionField), if you want the field required you can pass the same validator with not_empty=True, for the moment I think this is a good solution, later on we may add a parameter but ATM this seems not too DRY to me. ;-) Thanks. Ciao Michele --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk -~----------~----~----~----~------~----~------~--~---
