encode/django-rest-framework
1
1
Fork 0
mirror of https://github.com/encode/django-rest-framework.git synced 2025-02-03 13:14:30 +03:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2501 from thedrow/patch-10

Browse Source 
Fixed typos in docstrings
This commit is contained in:
Xavier Ordoquy 2015-02-02 10:00:24 +01:00
commit 0a805d979d
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
rest_framework/serializers.py
View File

@ -633,11 +633,11 @@ def raise_errors_on_nested_writes(method_name, serializer, validated_data):
If we don't do this explicitly they'd get a less helpful error when If we don't do this explicitly they'd get a less helpful error when
calling `.save()` on the serializer. calling `.save()` on the serializer.
We don't *automatically* support these sorts of nested writes brecause We don't *automatically* support these sorts of nested writes because
there are too many ambiguities to define a default behavior. there are too many ambiguities to define a default behavior.
Eg. Suppose we have a `UserSerializer` with a nested profile. How should Eg. Suppose we have a `UserSerializer` with a nested profile. How should
we handle the case of an update, where the `profile` realtionship does we handle the case of an update, where the `profile` relationship does
not exist? Any of the following might be valid: not exist? Any of the following might be valid:
* Raise an application error. * Raise an application error.