o h@sddlZddlmZddlmZddlmZddlm Z ddl m Z ddl m Z ddlmZGd d d ZGd d d eZGd ddeZGdddeZGdddeZGdddeZdS)N) gettext_lazy) exceptions)unicode_http_header_reverse) api_settings)replace_query_param) _MediaTypec@s8eZdZejZejZejZ ddZ dddZ ddZ dS) BaseVersioningcOsd}t|j|jjd)Nz.{cls}.determine_version() must be implemented.)cls)NotImplementedErrorformat __class____name__)selfrequestargskwargsmsgrY/var/www/html/premium_crap/venv/lib/python3.10/site-packages/rest_framework/versioning.pydetermine_versionsz BaseVersioning.determine_versionNcKst|||||fi|SNrrviewnamerrrr extrarrrreverseszBaseVersioning.reversecCs&|jsdS|dur||jkp||jvS)NT)allowed_versionsdefault_version)rversionrrris_allowed_versions z!BaseVersioning.is_allowed_versionNNNN) r __module__ __qualname__rDEFAULT_VERSIONrALLOWED_VERSIONSr VERSION_PARAM version_paramrrr rrrrr s  r c@s eZdZdZedZddZdS)AcceptHeaderVersioningzb GET /something/ HTTP/1.1 Host: example.com Accept: application/json; version=1.0 z#Invalid version in "Accept" header.cOs>t|j}|j|j|j}t|}||st |j |Sr) r accepted_media_typeparamsgetr'rrr r NotAcceptableinvalid_version_message)rrrr media_typerrrrr*s   z(AcceptHeaderVersioning.determine_versionN)rr"r#__doc___r-rrrrrr("s r(c2eZdZdZedZddZdfdd ZZS) URLPathVersioninga8 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[v1|v2]+)/users/$', users_list, name='users-list'), re_path(r'^(?P[v1|v2]+)/users/(?P[0-9]+)/$', users_detail, name='users-detail') ] GET /1.0/something/ HTTP/1.1 Host: example.com Accept: application/json zInvalid version in URL path.cOs8||j|j}|dur|j}||st|j|Sr)r+r'rr rNotFoundr-rrrrrrrrrIs   z#URLPathVersioning.determine_versionNc s:|jdur|j|ji|p i}tj|||||fi|Sr)rr'superrrrrrrRs  zURLPathVersioning.reverser! rr"r#r/r0r-rr __classcell__rrr6rr26s  r2cs:eZdZdZedZddZd fdd Zdd ZZ S) NamespaceVersioninga 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//', 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 zBInvalid version in URL path. Does not match any version namespace.cOsTt|dd}|dus |js|jS|jd}|D] }||r#|Sqt|j)Nresolver_match:)getattr namespacersplitr rr3r-)rrrrr:possible_versionsrrrrrxs    z%NamespaceVersioning.determine_versionNc s2|jdur |||}tj|||||fi|Sr)rget_versioned_viewnamer5rrr6rrrs   zNamespaceVersioning.reversecCs|jd|S)Nr;)r)rrrrrrr@sz*NamespaceVersioning.get_versioned_viewnamer!) rr"r#r/r0r-rrr@r8rrr6rr9^s  r9c@s*eZdZdZedZedZddZ dS)HostNameVersioningzX GET /something/ HTTP/1.1 Host: v1.example.com Accept: application/json z,^([a-zA-Z0-9]+)\.[a-zA-Z0-9]+\.[a-zA-Z0-9]+$zInvalid version in hostname.c OsN|d\}}}|j|}|s|jS|d}||s%t|j |S)Nr;) get_host partitionhostname_regexmatchrgroupr rr3r-) rrrrhostname separatorportrFrrrrrs    z$HostNameVersioning.determine_versionN) rr"r#r/recompilerEr0r-rrrrrrAs   rAcr1) QueryParameterVersioningza GET /something/?version=0.1 HTTP/1.1 Host: example.com Accept: application/json z#Invalid version in query parameter.cOs,|j|j|j}||st|j|Sr) query_paramsr+r'rr rr3r-r4rrrrs  z*QueryParameterVersioning.determine_versionNc s:tj|||||fi|}|jdurt||j|jS|Sr)r5rrrr')rrrrrr rurlr6rrrs  z QueryParameterVersioning.reverser!r7rrr6rrMs rM)rKdjango.utils.translationrr0rest_frameworkrrest_framework.compatrrest_framework.reverserrest_framework.settingsr*rest_framework.templatetags.rest_frameworkrrest_framework.utils.mediatypesr r r(r2r9rArMrrrrs       (1