On 31/03/2006, at 11:55, Michele Cella wrote: > ATM I can see only two solutions: > > 1) Removing the ignore_key_missing parameter from our Schema and tweak > thing so that this will work, since we don't let the Schema accept > missing fields the validation will be done by the widget validator and > if not_empty=True you will receive an error otherwise all should work > well.
+1 I personally never use disabled_fields and I'd like the extra sanitizing that will take place if missing keys are not ignored. > > 2) Hack our CheckBoxList (and MultipleSelectField) so that they use an > hidden field with the same name and value "tg_empty" then in > NestedFilter we walk c.p.params and search if this paramter is present > and alone, if it's the only one there we replace it with an empty > string '' otherwise we strip it out. > This feels really hackish to me and I would really like to avoid the > need for such a thing. The first word says it all.... I'd rather do 1) > > PS > I will offline starting today until Monday. :-) have a nice weekend > guys. You too ;) Alberto --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
