mirror of
https://github.com/encode/django-rest-framework.git
synced 2024-12-01 22:14:06 +03:00
fixed typo
This commit is contained in:
parent
abf7f11619
commit
a967187b41
|
@ -100,7 +100,7 @@ Add the following field to the serializer definition:
|
||||||
|
|
||||||
**Note**: Make sure you also add `'owner',` to the list of fields in the inner `Meta` class.
|
**Note**: Make sure you also add `'owner',` to the list of fields in the inner `Meta` class.
|
||||||
|
|
||||||
This field is doing something quite interesting. The `source` argument controls which attribtue is used to populate a field, and can point at any attribute on the serialized instance. It can also take the dotted notation shown above, in which case it will traverse the given attributes, in a similar way as is used with Django's template language.
|
This field is doing something quite interesting. The `source` argument controls which attribute is used to populate a field, and can point at any attribute on the serialized instance. It can also take the dotted notation shown above, in which case it will traverse the given attributes, in a similar way as is used with Django's template language.
|
||||||
|
|
||||||
The field we've added is the untyped `Field` class, in contrast to the other typed fields, such as `CharField`, `BooleanField` etc... The untyped `Field` is always read-only, and will be used for serialized representations, but will not be used for updating model instances when they are deserialized.
|
The field we've added is the untyped `Field` class, in contrast to the other typed fields, such as `CharField`, `BooleanField` etc... The untyped `Field` is always read-only, and will be used for serialized representations, but will not be used for updating model instances when they are deserialized.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue
Block a user