o
    i[                     @   sp   d dl mZmZmZ d dlmZ d dlmZmZm	Z	 ddl
mZ dddid	d
ddidgZG dd deZdS )    )AnyDictOptional)	BaseModel)PYDANTIC_V2
ConfigDictExtra   )ServergetUserAddressByUUIDuserUuidz$response.body#/uuid)operationId
parametersz+#/paths/~12.0~1repositories~1{username}/getusernamez$response.body#/username)operationRefr   c                   @   s   e Zd ZU dZdZee ed< 	 dZee ed< 	 dZ	ee
eef  ed< 	 dZee ed< 	 dZee ed< 	 dZee ed< 	 erMed	d
eidZdS G dd dZdS )Linka  
    The `Link object` represents a possible design-time link for a response.
    The presence of a link does not guarantee the caller's ability to successfully
    invoke it, rather it provides a known relationship and traversal mechanism between
    responses and other operations.

    Unlike _dynamic_ links (i.e. links provided **in** the response payload),
    the OAS linking mechanism does not require link information in the runtime response.

    For computing links, and providing instructions to execute them,
    a [runtime expression](#runtimeExpression) is used for accessing values in an
    operation and using them as parameters while invoking the linked operation.
    Nr   r   r   requestBodydescriptionserverallowexamples)extrajson_schema_extrac                   @   s   e Zd ZejZdeiZdS )zLink.Configr   N)__name__
__module____qualname__r   r   r   	_examplesschema_extra r   r   c/var/www/html/karishye-ai-python/venv/lib/python3.10/site-packages/openapi_pydantic/v3/v3_1/link.pyConfig]   s    r    )r   r   r   __doc__r   r   str__annotations__r   r   r   r   r   r   r   r
   r   r   r   model_configr    r   r   r   r   r      s(   
 	
r   N)typingr   r   r   pydanticr   openapi_pydantic.compatr   r   r   r   r
   r   r   r   r   r   r   <module>   s    