จากวิวแบบฟังก์ชันสู่วิวแบบคลาส

So far your views were plain functions. Django also lets you write views as classes, which package related logic together neatly.

A class-based view (CBV) is just a Python class that handles a request. Django turns it into a callable for you behind the scenes.

Function views often repeat the same shape: fetch data, build context, render a template. CBVs let you reuse that shape instead of copying it.

Here is a familiar function view. It takes a request and returns a response, all in one block.

As a class, you subclass View and define a method per HTTP verb. The logic is the same, just organized differently.

In a CBV, a get method handles GET requests and a post method handles POST. No more giant if-checks on request.method.

Because CBVs are classes, you can subclass and override only what changes. Shared behavior lives in a parent class once.

Django includes ready-made generic views like ListView and DetailView. They cover common patterns so you write almost no code.

For a tiny, one-off view, a function is often clearer. Reach for CBVs when logic repeats or grows complex.

Both styles get wired the same way in urls. A CBV just needs as_view() to become a callable Django can route to.

CBVs are not better or worse, just different. Choose based on reuse: repeated patterns favor classes, simple pages favor functions.

What is the main reason class-based views exist?

You met class-based views: classes that handle requests, map methods to HTTP verbs, and reuse logic through inheritance. Great when patterns repeat. 🎯