Apa iku DRF viewsets lan routers?

Question

Accepted Answer

Ing Django REST Framework, **viewsets** nglumpukake logika kanggo saperangan endpoint API sing ana gandheng (operasi CRUD kanggo sumber) dadi siji klas, lan **routers** ngasilake routing URL kanggo sakabehane kanthi otomatis. Babarengan-babarengan samubarang, padha nyuda boilerplate kanthi dramatis kanggo mbangun REST APIs.

## ModelViewSet — CRUD lengkap ing sawetara baris

```python
from rest_framework import viewsets

class ArticleViewSet(viewsets.ModelViewSet):
    queryset = Article.objects.all()             # the data
    serializer_class = ArticleSerializer          # how to serialize it
    # That's it! This provides ALL standard CRUD endpoints automatically:
    #   list (GET), create (POST), retrieve (GET /id), update (PUT/PATCH /id), destroy (DELETE /id)
```

A `ModelViewSet` nyediakake kanthi otomatis **rangkaian lengkap endpoint RESTful CRUD** kanggo model — list, create, retrieve, update, partial update, lan delete — saka mung queryset lan serializer. Ora perlu nulis saben view kanthi kapisahan.

## Routers — pembuatan URL otomatis

```python
from rest_framework.routers import DefaultRouter

router = DefaultRouter()
router.register(r"articles", ArticleViewSet)     # register the viewset

urlpatterns = router.urls
# automatically creates the RESTful URLs:
#   GET    /articles/        → list
#   POST   /articles/        → create
#   GET    /articles/{id}/   → retrieve
#   PUT    /articles/{id}/   → update
#   PATCH  /articles/{id}/   → partial update
#   DELETE /articles/{id}/   → destroy
```

A **router** nggambarake viewset menyang rangkaian lengkap URL RESTful standar kanthi otomatis — registering siji viewset ngasilake kabeh endpoint konvensional kanthi HTTP methods sing bener, ngilangi konfigurasi URL manual.

## Customizing viewsets

```python
class ArticleViewSet(viewsets.ModelViewSet):
    serializer_class = ArticleSerializer
    permission_classes = [IsAuthenticated]        # authorization

def get_queryset(self):                        # customize the data per request
        return Article.objects.filter(author=self.request.user)

# add CUSTOM endpoints beyond CRUD with @action
    @action(detail=True, methods=["post"])
    def publish(self, request, pk=None):           # POST /articles/{id}/publish/
        article = self.get_object()
        article.published = True
        article.save()
        return Response({"status": "published"})
```

Viewsets dikustomisasi dening override methods (`get_queryset`, `perform_create`), setting permissions, lan nambah **custom actions** (`@action`) kanggo endpoints nang sajroning standar CRUD.

## Viewsets vs generic API views

```text
ModelViewSet  → ALL CRUD in one class + router → least code for standard REST resources
Generic views (ListCreateAPIView, etc.) → more explicit, one class per endpoint group
APIView       → full manual control for non-standard/custom endpoints
→ Use viewsets+routers for conventional REST resources; generic/APIView for custom needs.
```

## Kenapa iki penting

Viewsets lan routers minangka fitur DRF sing kuat kanggo mbangun REST APIs kanthi efisien — samubarang mwakilake tingkat abstraksi paling dhuwur kanggo kasus sing sempurna umum yaiku nglumpukake model minangka sumber REST lengkap, lan ngerti samubarang iki aji kanggo pangembangan API sing produktif.

Manfaat utama yaiku **boilerplate reduction** sing dramatis: `ModelViewSet` plus router menehi sampeyan complete, conventional REST API kanggo sumber (kabeh endpoint CRUD kanthi HTTP methods lan URLs sing bener) saka mung queryset lan serializer — ngganteni apa sing carane saiki bakal lawas sawetara views lan manual URL patterns.

Iki ndadekake mbangun standar REST APIs luar biasa cepet lan memastikan **RESTful conventions** (URL structure konsisten lan HTTP method semantics) ditindakake kanthi otomatis.

Viewsets tetep luwes — sampeyan customize samubarang dening override methods (filtering queryset per user, ngontrol permissions, hooking menyang create/update) lan nambah **custom actions** (`@action`) kanggo endpoints nang sajroning CRUD dasar.

Ngerti viewsets lan routers, cara samubarang ngasilake endpoints, cara customize samubarang, lan **kapan nggunakake samubarang** (conventional REST resources) versus explicit generic views utawa APIView (custom/non-standard endpoints) minangka ilmu praktis penting kanggo pangembangan DRF.

Sameyan mbangun REST APIs minangka panggunaan utama Django saiki, lan viewsets+routers minangka cara idiomatic, paling produktif kanggo samubarang kanggo standar resources, samubarang minangka layak-digunakake, bagian penting saka DRF toolkit sing ndadekake pangembang mbangun APIs kuat kanthi minimal code saengga tetep nduwe luwes kanggo ngangkat kebutuhan custom.