diff options
| author | Omer Katz | 2015-02-02 10:50:54 +0200 |
|---|---|---|
| committer | Omer Katz | 2015-02-02 10:50:54 +0200 |
| commit | 8f1d42e7d5146e19842d2837259284f8730b451d (patch) | |
| tree | 1fd4244b7eef02110e84eda63c2fc0b9d4c83663 | |
| parent | 6e2ea852d0deb178d60035c139b689a2ece12c70 (diff) | |
| download | django-rest-framework-8f1d42e7d5146e19842d2837259284f8730b451d.tar.bz2 | |
Fixed typos in docstrings.
| -rw-r--r-- | rest_framework/serializers.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/rest_framework/serializers.py b/rest_framework/serializers.py index 42d1e370..2fd907ec 100644 --- a/rest_framework/serializers.py +++ b/rest_framework/serializers.py @@ -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 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. 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: * Raise an application error. |
