rest_framework.versioning.URLPathVersioning

class documentation

class URLPathVersioning(BaseVersioning): (source)

View In Hierarchy

To the client this is the same style as `NamespaceVersioning`. The difference is in the backend - this implementation uses Django's URL keyword arguments to determine the version. An example URL conf for two views that accept two different versions. urlpatterns = [ re_path(r'^(?P<version>[v1|v2]+)/users/$', users_list, name='users-list'), re_path(r'^(?P<version>[v1|v2]+)/users/(?P<pk>[0-9]+)/$', users_detail, name='users-detail') ] GET /1.0/something/ HTTP/1.1 Host: example.com Accept: application/json

Method determine_version 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 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