DRFDocs not showing delete, post, etc. options but regular docs do?

Heyo! Thanks so much for releasing this, it is beautiful.

I am a little confused on why I’m not seeing POST/DELETE/etc. on the DRF docs version, but I can see it on the regular API docs:

Looks like I can only do GET/OPTIONS?

Here’s some code:

from rest_framework import viewsets, mixins

from api import serializers
from competitions.models import Competition


class CompetitionViewSet(mixins.ListModelMixin,
                         mixins.CreateModelMixin,
                         mixins.UpdateModelMixin,
                         mixins.DestroyModelMixin,
                         viewsets.GenericViewSet):
    """Tyler loves pizza!!!"""
    queryset = Competition.objects.all()
    serializer_class = serializers.CompetitionSerializer

from django.conf.urls import url, include
from rest_framework import routers

from . import views


router = routers.DefaultRouter()
router.register(r'competitions', views.CompetitionViewSet)

urlpatterns = [
    url(r'^', include(router.urls)),

    url(r'^api-auth/', include('rest_framework.urls', namespace='rest_framework')),

    url(r'^docs/', include('rest_framework_docs.urls')),
]

It’s probably something silly I’m overlooking, thanks!

[ckcollab]

Using this combination of classes seems to work:

from rest_framework.viewsets import GenericViewSet
from rest_framework.generics import ListAPIView, CreateAPIView, RetrieveAPIView, DestroyAPIView


class DataViewSet(ListAPIView, CreateAPIView, RetrieveAPIView, DestroyAPIView, GenericViewSet):
    pass

I think that this is about the same behavior, just different classes… that seem to work? This is for a simple dummy app that does nothing, so I’m not sure if this breaks other things.

[ckcollab]

No, no updates here. We need a way to help maintainers get updates through… some kind of reward system…