aboutsummaryrefslogtreecommitdiffstats
path: root/docs/tutorial/1-serialization.md
diff options
context:
space:
mode:
authorTom Christie2013-05-30 11:34:09 +0100
committerTom Christie2013-05-30 11:34:09 +0100
commit441cdf80653446254703dc23e831b21036f22b31 (patch)
tree4cf63fe8e302d8af44b1dc45f95c82ccf491ba67 /docs/tutorial/1-serialization.md
parent8d4bcb4b4c837f9deb5f81d7af6a397405aa07fa (diff)
downloaddjango-rest-framework-441cdf80653446254703dc23e831b21036f22b31.tar.bz2
Note widget attribute on serializer field. Closes #836.
Diffstat (limited to 'docs/tutorial/1-serialization.md')
-rw-r--r--docs/tutorial/1-serialization.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/docs/tutorial/1-serialization.md b/docs/tutorial/1-serialization.md
index 3382deea..780ad4b7 100644
--- a/docs/tutorial/1-serialization.md
+++ b/docs/tutorial/1-serialization.md
@@ -146,6 +146,8 @@ The first thing we need to get started on our Web API is provide a way of serial
The first part of serializer class defines the fields that get serialized/deserialized. The `restore_object` method defines how fully fledged instances get created when deserializing data.
+Notice that we can also use various attributes that would typcially be used on form fields, such as `widget=widgets.Testarea`. These can be used to control how the serializer should render when displayed as an HTML form.
+
We can actually also save ourselves some time by using the `ModelSerializer` class, as we'll see later, but for now we'll keep our serializer definition explicit.
## Working with Serializers