Proofread changes to docs/forms.txt from [3792]
git-svn-id: http://code.djangoproject.com/svn/django/trunk@3838 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
321a59a36a
commit
a0b78df2bb
|
@ -481,13 +481,13 @@ the data being validated.
|
||||||
Also, because consistency in user interfaces is important, we strongly urge you
|
Also, because consistency in user interfaces is important, we strongly urge you
|
||||||
to put punctuation at the end of your validation messages.
|
to put punctuation at the end of your validation messages.
|
||||||
|
|
||||||
When Are Validators Called?
|
When are validators called?
|
||||||
---------------------------
|
---------------------------
|
||||||
|
|
||||||
After a form has been submitted, Django first checks to see that all the
|
After a form has been submitted, Django first checks to see that all the
|
||||||
required fields are present and non-empty. For each field that passes that
|
required fields are present and non-empty. For each field that passes that
|
||||||
test *and if the form submission contained data* for that field, all the
|
test *and if the form submission contained data* for that field, all the
|
||||||
validators for that field are called in turn. The emphasised portion in the
|
validators for that field are called in turn. The emphasized portion in the
|
||||||
last sentence is important: if a form field is not submitted (because it
|
last sentence is important: if a form field is not submitted (because it
|
||||||
contains no data -- which is normal HTML behaviour), the validators are not
|
contains no data -- which is normal HTML behaviour), the validators are not
|
||||||
run against the field.
|
run against the field.
|
||||||
|
@ -497,13 +497,12 @@ This feature is particularly important for models using
|
||||||
``forms.CheckBoxField``. If the checkbox is not selected, it will not
|
``forms.CheckBoxField``. If the checkbox is not selected, it will not
|
||||||
contribute to the form submission.
|
contribute to the form submission.
|
||||||
|
|
||||||
If you would like your validator to *always* run, regardless of whether the
|
If you would like your validator to run *always*, regardless of whether its
|
||||||
field it is attached to contains any data, set the ``always_test`` attribute
|
attached field contains any data, set the ``always_test`` attribute on the
|
||||||
on the validator function. For example::
|
validator function. For example::
|
||||||
|
|
||||||
def my_custom_validator(field_data, all_data):
|
def my_custom_validator(field_data, all_data):
|
||||||
# ...
|
# ...
|
||||||
|
|
||||||
my_custom_validator.always_test = True
|
my_custom_validator.always_test = True
|
||||||
|
|
||||||
This validator will always be executed for any field it is attached to.
|
This validator will always be executed for any field it is attached to.
|
||||||
|
|
Loading…
Reference in New Issue