Two Scoops Study Session 7

Based on Chapter 10 of Two Scoops of Django, this session summarized how to use class-based views (CBV). The core idea is to keep view code as short as possible, avoid repeating the same code, put business logic in the model, and keep views simple and clear.

When using CBVs, you need to clearly understand the roles of inheritance and mixins. A mixin is not an instantiated class but a class that provides functionality, and the inheritance order is processed from left to right. Understanding this order and MRO lets you predict which method gets called first.

Django's built-in CBVs should be chosen according to their purpose.

• View: a basic view usable anywhere
• RedirectView: redirects to another URL
• TemplateView: renders a template
• ListView / DetailView: object lists and detail views
• FormView / CreateView / UpdateView / DeleteView: form handling and CRUD
• generic date view: chronological ordering

Practical tips were also covered. For views that require authentication, use LoginRequiredMixin from django-braces, add custom actions via form_valid(), and use the view object's methods and attributes to flexibly control the rendering flow. For more complex configurations, libraries like django-extra-views can help.

In the latter part, the discussion covered how a project can be built using only django.views.generic.View, and shared the experience of manually working through the MRO algorithm to understand call order. Rather than simply accepting the book's principles as correct, reviewing together why things actually work that way turned out to be a valuable learning experience.