mirror of
https://github.com/encode/django-rest-framework.git
synced 2024-11-22 17:47:04 +03:00
Fixed typos in docstrings.
This commit is contained in:
parent
6e2ea852d0
commit
8f1d42e7d5
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue
Block a user