Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:59:30 +0100] rev 4664
#714109: [selectors] non_final_entity should implement score_class
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:52:57 +0100] rev 4663
merge
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:52:40 +0100] rev 4662
add XXX note
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:51:20 +0100] rev 4661
[form] cache field value in form.formvalues using (field, form) key since in some case the same field instance may be shared accross multiple forms, which may share the formvalues dict in case of sub-forms
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:49:37 +0100] rev 4660
cleanup
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:46:56 +0100] rev 4659
[form] complete 25de2eb0432b by ignore req parameters by default for all hidden fields
Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Feb 2010 12:43:15 +0100] rev 4658
[form] add a new ignore_req_params attribute on field controlling value's retreival
for such field, such as eid/__type in entity forms, we don't want to consider values
from req.form since we may get undesired value (as reported by #714766). This new
attribute allow do specify that we don't want to consider req.form in such case.
Also, it seems that retreival of form values after a validation error suffer from
the same problem, so don't use form_previous_values for field with ignore_req_params
set to True (XXX though I suppose that may not be correct in some cases).