Re: Why filter_extra_fields does not imply allow_extra_fields?
Jon Nelson <jnelson+formencode-l78HVRKxS1/[email protected]> Thu, 19 Nov 2009 18:37:01 -0600
| Newsgroups | gmane.comp.python.formencode |
|---|---|
| Message-ID | <[email protected]> |
On Thu, Nov 19, 2009 at 4:10 PM, Ian Bicking <[email protected]> wrote: > On Thu, Nov 19, 2009 at 2:53 PM, Nicolas Grilly > <nicolas-u/[email protected]> wrote: > > I'm wondering why filter_extra_fields=True does not imply > > allow_extra_fields=True? There is nothing to filter if extra fields > > are not allowed, isn't it? Am I missing something or is it possible to > > propose this change to FormEncode? > > There's no real reason for it. FormEncode is on bitbucket now, if you > I disagree. filter_extra_fields = True is useful when you want to take a dictionary which might have a whole bunch of keys in it and, provided the form validates, turn out the other end *just* the validated keys. allow_extra_fields turns the condition of any extra field into an error. At least that's how I think it works. -- Jon ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ FormEncode-discuss mailing list FormEncode-discuss-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/formencode-discuss