mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 02:48:35 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Used consistent capitalization and hyphenation of "class-based views" in docs.

Browse source
This commit is contained in:
Anton Strogonoff 2015-08-19 02:01:36 +06:00 • committed by Tim Graham
parent 39b55537ec
commit 20787b5c29
11 changed files with 14 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/topics/class-based-views/generic-display.txt
View file

@ -1,7 +1,7 @@
.. _Generic views:
==================================
Built-in Class-based generic views
Built-in class-based generic views
==================================
Writing Web applications can be monotonous, because we repeat certain patterns

2
docs/topics/class-based-views/index.txt
View file

@ -84,7 +84,7 @@ views::
For more information on how to use the built in generic views, consult the next
topic on :doc:`generic class based views</topics/class-based-views/generic-display>`.
topic on :doc:`generic class-based views</topics/class-based-views/generic-display>`.
.. _supporting-other-http-methods:

4
docs/topics/class-based-views/intro.txt
View file

@ -1,5 +1,5 @@
=================================
Introduction to Class-based views
Introduction to class-based views
=================================
Class-based views provide an alternative way to implement views as Python
@ -43,7 +43,7 @@ The toolkit of base classes and mixins that Django uses to build class-based
generic views are built for maximum flexibility, and as such have many hooks in
the form of default method implementations and attributes that you are unlikely
to be concerned with in the simplest use cases. For example, instead of
limiting you to a class based attribute for ``form_class``, the implementation
limiting you to a class-based attribute for ``form_class``, the implementation
uses a ``get_form`` method, which calls a ``get_form_class`` method, which in
its default implementation just returns the ``form_class`` attribute of the
class. This gives you several options for specifying what form to use, from a

5
docs/topics/class-based-views/mixins.txt
View file

@ -204,11 +204,10 @@ the box.
understandable to someone else coming to it later, and with fewer
interactions to worry about you will save yourself some thinking. (Of
course, you can always dip into Django's implementation of the generic
class based views for inspiration on how to tackle problems.)
class-based views for inspiration on how to tackle problems.)
.. _method resolution order: https://www.python.org/download/releases/2.3/mro/
Using SingleObjectMixin with View
---------------------------------
@ -593,7 +592,7 @@ views as separate as possible.
More than just HTML
===================
Where class based views shine is when you want to do the same thing many times.
Where class-based views shine is when you want to do the same thing many times.
Suppose you're writing an API, and every view should return JSON instead of
rendered HTML.