From ddcf4c89d8ab67b3338b3ce4e05dc7bfb563b377 Mon Sep 17 00:00:00 2001 From: Kenneth Schnall Date: Thu, 7 Jul 2016 15:06:43 -0400 Subject: [PATCH] Update serializers.md --- docs/api-guide/serializers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-guide/serializers.md b/docs/api-guide/serializers.md index 038a4d6b9..70fab448c 100644 --- a/docs/api-guide/serializers.md +++ b/docs/api-guide/serializers.md @@ -876,7 +876,7 @@ There are four methods that can be overridden, depending on what functionality y * `.to_internal_value()` - Override this to support deserialization, for write operations. * `.create()` and `.update()` - Override either or both of these to support saving instances. -Because this class provides the same interface as the `Serializer` class, you can use it with the existing generic class based views exactly as you would for a regular `Serializer` or `ModelSerializer`. +Because this class provides the same interface as the `Serializer` class, you can use it with the existing generic class-based views exactly as you would for a regular `Serializer` or `ModelSerializer`. The only difference you'll notice when doing so is the `BaseSerializer` classes will not generate HTML forms in the browsable API. This is because the data they return does not include all the field information that would allow each field to be rendered into a suitable HTML input.