Kaydet (Commit) 05737128 authored tarafından Gary Wilson Jr's avatar Gary Wilson Jr

Fixed #9902 -- Corrected misspelling in form validation documentation, thanks zunzun.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@9674 bcc190cf-cafb-0310-a4f2-bffc1f526a37
üst bcae5fc1
...@@ -291,7 +291,7 @@ extra design effort to create a sensible form display. The details are worth ...@@ -291,7 +291,7 @@ extra design effort to create a sensible form display. The details are worth
noting, however. Firstly, earlier we mentioned that you might need to check if noting, however. Firstly, earlier we mentioned that you might need to check if
the field name keys already exist in the ``_errors`` dictionary. In this case, the field name keys already exist in the ``_errors`` dictionary. In this case,
since we know the fields exist in ``self.cleaned_data``, they must have been since we know the fields exist in ``self.cleaned_data``, they must have been
valid when cleaned as individual fields, so there will be no corresonding valid when cleaned as individual fields, so there will be no corresponding
entries in ``_errors``. entries in ``_errors``.
Secondly, once we have decided that the combined data in the two fields we are Secondly, once we have decided that the combined data in the two fields we are
...@@ -302,4 +302,3 @@ In fact, Django will currently completely wipe out the ``cleaned_data`` ...@@ -302,4 +302,3 @@ In fact, Django will currently completely wipe out the ``cleaned_data``
dictionary if there are any errors in the form. However, this behaviour may dictionary if there are any errors in the form. However, this behaviour may
change in the future, so it's not a bad idea to clean up after yourself in the change in the future, so it's not a bad idea to clean up after yourself in the
first place. first place.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment