o &zh@sddlZddlZddlmZmZmZddlmZddlm Z ddl m Z ddl m ZddlmZddlmZmZdd lmZdd lmZddlm Z dd lmZGd d d eZddZdS)N)AnyDictOptional)get_user_model)models)Field) app_settings) EmailAddress) user_display user_username) BaseAdapter)default_get_frontend_url)import_attributec @s\eZdZdZdddddejddd d d Zd eee ffd dZ ddZ ddZ ddZ dS)DefaultHeadlessAdapteraBThe adapter class allows you to override various functionality of the ``allauth.headless`` app. To do so, point ``settings.HEADLESS_ADAPTER`` to your own class that derives from ``DefaultHeadlessAdapter`` and override the behavior by altering the implementation of the methods according to your own need. zUnknown account.z`client_id` required.zInvalid token.z/Provider does not support token authentication.z*`id_token` and/or `access_token` required.requiredzUnknown email address.zUnknown provider.z Invalid URL.) account_not_foundclient_id_required invalid_token"token_authentication_not_supportedtoken_requiredr unknown_emailunknown_provider invalid_urlreturncCsddt||DS)a Returns the basic user data. Note that this data is also exposed in partly authenticated scenario's (e.g. password reset, email verification). Do not override this method if you would like your customized user payloads to be reflected in the (dynamically rendered) OpenAPI specification. In that case, override ``get_user_dataclass()`` and ``user_as_dataclass`` instead. cSsi|] \}}|dvr||qS))N).0kvrrS/var/www/html/kangema/venv/lib/python3.10/site-packages/allauth/headless/adapter.py 1s z9DefaultHeadlessAdapter.serialize_user..) dataclassesasdictuser_as_dataclassitems)selfuserrrrserialize_user's z%DefaultHeadlessAdapter.serialize_usercKst|j|fi|S)z/Return the frontend URL for the given URL name.)r request)r%urlnamekwargsrrrget_frontend_url7sz'DefaultHeadlessAdapter.get_frontend_urlcCs|}i}t}t|jj}|jsd}nt|tjr|j}nt|j}t j r-t ||d<|jr7t j |}nd}|||r@|ndt||d|di|S)z See ``get_user_dataclass()``. This method returns an instance of that ``dataclass``, populated with the given ``user`` fields. Nusername)idemaildisplayhas_usable_passwordr)get_user_dataclassrtype_metapk issubclassr IntegerFieldstraccount_settingsUSER_MODEL_USERNAME_FIELDr r objectsget_primary_emailupdater r0)r%r&UserDcr*Userpk_field_classid_dcr.rrrr#;s,     z(DefaultHeadlessAdapter.user_as_dataclassc Csg}t}t|jj}t|tjrt}tt }nt|tj r%t }d}nt}d}dd}| |dt |d||dtdd |d t td d |d tddgtjr[||dtddtd|S)a Basic user data payloads are exposed in some of the headless responses. If you need to customize these payloads in such a way that your custom user payload is also reflected in the OpenAPI specification, you wil need to provide a ``dataclass`` representing the schema of your custom payload, as well as method that takes a ``User`` instance and wraps it into your dataclass. This method returns that ``dataclass``. {uidcSs||tj||ddfS)N) descriptionexample)metadata)r!field)attrtyprCrDrrrdc_fieldpsz;DefaultHeadlessAdapter.get_user_dataclass..dc_fieldr-z The user ID.r/zThe display name for the user.z Magic Wizardr.zThe email address.zemail@domain.orgr0z.Whether or not the account has a password set.Tr,z The username.wizardr>)rr2r3r4r5r UUIDFieldr7uuiduuid4r6intextendrboolr8r9appendr!make_dataclass)r%fieldsr>r?id_type id_examplerIrrrr1Zs>       z)DefaultHeadlessAdapter.get_user_dataclassN)__name__ __module__ __qualname____doc__rdefault_error_messageserror_messagesrr7rr'r+r#r1rrrrrs   rcCs ttjS)N)rrADAPTERrrrr get_adapters r])r!rLtypingrrrdjango.contrib.authr django.dbrdjango.forms.fieldsrallauth.accountrr8allauth.account.modelsr allauth.account.utilsr r allauth.core.internal.adapterr allauth.core.internal.httpkitr allauth.headless allauth.utilsrrr]rrrrs