Django Rest Framework：能否用单个视图集处理多类型HTTP请求？

Great question! Your initial judgment is spot-on—creating two separate views is a perfectly valid (and often recommended) approach for this scenario. But depending on the REST framework you’re using (I’ll focus on Django REST Framework here since your endpoint structure aligns with common patterns), you do have the option to handle both sets of actions in a single view class if you prefer, though splitting things up is usually better for long-term maintainability.

Let’s break down both options clearly:

Option 1: Separate Views (Recommended) #

This approach follows the Single Responsibility Principle, keeping each view focused on one job. It’s easier to debug, test, and extend as your app grows:

• List View: Handles only the GET /account/items request to fetch the resource list.
• Detail Action View: Handles the custom POST and PATCH operations on /account/items/<pk>/.

Example Code (Django REST Framework) #

Views.py

from rest_framework.generics import ListAPIView, GenericAPIView
from rest_framework.response import Response
from .models import Item
from .serializers import ItemSerializer

class ItemListView(ListAPIView):
    queryset = Item.objects.all()
    serializer_class = ItemSerializer

class ItemCustomActionView(GenericAPIView):
    queryset = Item.objects.all()
    
    def post(self, request, pk):
        item = self.get_object()
        # Replace with your custom POST logic (e.g., trigger a workflow for the item)
        return Response({"status": "Custom POST action executed successfully"})
    
    def patch(self, request, pk):
        item = self.get_object()
        # Replace with your custom PATCH logic (e.g., update a specific status field)
        return Response({"status": "Custom PATCH action executed successfully"})

Urls.py

from django.urls import path
from .views import ItemListView, ItemCustomActionView

urlpatterns = [
    path('account/items/', ItemListView.as_view(), name='item-list'),
    path('account/items/<int:pk>/', ItemCustomActionView.as_view(), name='item-custom-actions'),
]

Option 2: Single View Class (Consolidated Approach) #

If you want to keep related endpoints grouped under one class, you can extend a base generic view and implement all required methods. However, this can make the view cluttered as you add more logic over time.

Example Code #

Views.py

from rest_framework.generics import GenericAPIView
from rest_framework.response import Response
from .models import Item
from .serializers import ItemSerializer

class ItemCombinedView(GenericAPIView):
    queryset = Item.objects.all()
    serializer_class = ItemSerializer
    
    def get(self, request):
        # Handle list retrieval
        queryset = self.get_queryset()
        serializer = self.get_serializer(queryset, many=True)
        return Response(serializer.data)
    
    def post(self, request, pk=None):
        # Block POST requests to the list endpoint (as per your requirement)
        if not pk:
            return Response({"error": "POST is not allowed on the list endpoint"}, status=405)
        item = self.get_object()
        # Custom POST logic here
        return Response({"status": "Custom POST action executed"})
    
    def patch(self, request, pk):
        item = self.get_object()
        # Custom PATCH logic here
        return Response({"status": "Custom PATCH action executed"})

Urls.py

from django.urls import path
from .views import ItemCombinedView

urlpatterns = [
    path('account/items/', ItemCombinedView.as_view(), name='item-combined'),
    path('account/items/<int:pk>/', ItemCombinedView.as_view(), name='item-combined-detail'),
]

Final Verdict #

Your initial plan to use two separate views is the better choice for most applications. It keeps your code clean, organized, and easier to maintain. The single-view approach is functional but should only be used if you have a specific reason to consolidate (e.g., extremely minimal logic for both endpoints).

内容的提问来源于stack exchange，提问作者aroooo