rest_framework.versioning.NamespaceVersioning

class documentation

class NamespaceVersioning(BaseVersioning): (source)

To the client this is the same style as `URLPathVersioning`. The difference is in the backend - this implementation uses Django's URL namespaces to determine the version. An example URL conf that is namespaced into two separate versions # users/urls.py urlpatterns = [ path('/users/', users_list, name='users-list'), path('/users/<int:pk>/', users_detail, name='users-detail') ] # urls.py urlpatterns = [ path('v1/', include('users.urls', namespace='v1')), path('v2/', include('users.urls', namespace='v2')) ] GET /1.0/something/ HTTP/1.1 Host: example.com Accept: application/json

Method	`determine_version`	Undocumented
Method	`get_versioned_viewname`	Undocumented
Method	`reverse`	Undocumented
Class Variable	`invalid_version_message`	Undocumented

Inherited from BaseVersioning:

Method is_allowed_version Undocumented

def determine_version(self, request, *args, **kwargs): (source) ¶

overrides rest_framework.versioning.BaseVersioning.determine_version

Undocumented

def get_versioned_viewname(self, viewname, request): (source) ¶

Undocumented

def reverse(self, viewname, args=None, kwargs=None, request=None, format=None, **extra): (source) ¶

overrides rest_framework.versioning.BaseVersioning.reverse

Undocumented

invalid_version_message = (source) ¶

Undocumented