o

|��g���@s 	Udd
lZdd
l
Z
ddlmZ
ddlmZ
ddlmZmZmZm	Z	
ddl
mZ
ddlm
Z

ddlmZmZmZmZmZmZ
ddlmZ
dd	lmZmZmZmZmZmZmZmZm Z m!Z!m"Z"m#Z#m$Z$m%Z%m&Z&m'Z'm(Z(m)Z)
dd
l*m+Z+
ddl,m-Z-m.Z.
ddl/m0Z0m1Z1m2Z2m3Z3m4Z4m5Z5m6Z6m7Z7m8Z8m9Z9m:Z:m;Z;m<Z<
dd
l=m>Z>
ddl?m@Z@mAZA
ddlBmCZCmDZDmEZEmFZFmGZGmHZHmIZImJZJmKZKmLZLmMZMmNZNmOZOmPZPmQZQmRZRmSZSmTZTmUZU
ddlVmWZWmXZXmYZYmZZZm[Z[m\Z\m]Z]m^Z^m_Z_
ddl`maZambZbmcZc
er�ddldmeZe
ddlfmgZg
dZhdZie(e&de&e
fZje$ejZkdedde!e<deelefdd
fdd�Zmdd
d
d
eid�d e#e(e&de&d!fd"end#e!eld$e!eld%e!eld&eldeeleffd'd(�Zodd
eifd)e(e&de&d!fd"end%e!eld&eldeeleff
d*d+�Zpd�de<d-ende%eelefenffd.d/�Zqdd
eid
d0�de<d"end1eejelfd%e!eld&eld2e!ekde%eelefeelefe$elffd3d�ZresetefZud4eud5fd6eud7fd8eld9ffZve%e%ele(ewe%ewd:ffelfd:fexd;<d<eud=fd>eud?fd@eudAfdBeudCfdDeudEffZye%e%ele(ewe%ewd:ffelfd:fexdF<de<deeleffdGdH�ZzdIekdeejelffdJdK�Z{d�d)e&dd2e!ekdekfdLdM�Z|de<d2ekdekfdNdO�Z}dPe#e<d2ekdekfdQdR�Z~d e#e&ddekfdSdT�Zd)ejdelfdUdV�Z�d,d
dW�de<d"end1eejelfd&eld-end%e!eld2ekde%eelefeelefe$elffdXdY�Z�dd
eid
d
dZ�d)ejd"end1eejelfd%e!eld&eld2e!ekde!e<de%eelefeelefe$elffd[d\�Z�d
d]�
d)e&dd"end1eejelfd&eld%e!eld2ekde%eelefeelefe$elffd^d_�Z�d
d`�
dae&e
de!e<deeleffdbdc�Z�d,d
dW�de<d"end1eejelfd&eld-end%e!eld2ekde%eelefeelefe$elffddde�Z�edfdgdh�fedfdidh�fedfdjdh�fedfdkdh�fe	dldmdh�fedfdndh�fedfdodh�fedfdpdh�fedfdqdh�fedfdrdh�fedfdsdh�fe"dfd8dh�feldtdfi
fe�dfdudh�fendtdvi
fesdtdwi
fetdtdli
fedtdli
fe+dfdxdh�fe�dtdyi
fe�dzid{�fe�dzid{�fe�dzidd|�fe�dzidd|�ffZ�e%e%eeeleffd:fexd}<dfd~dh�Z�ded�eelefdd
fd�d��Z�d�eld%e!eld&eld-endeeleff
d�d��Z�d,d
dW�de<d"end1eejelfd&eld-end%e!eld2ekde%eelefeelefe$elffd�d��Z�d�e%ed:fde<de<fd�d��Z�d�edefd�d��Z�eseRetePeeOiZ�eeed:ewffexd�<	,d�d�ed�e;d�eld�ende&ef
d�d��Z�d�ed�e;de%e&ee$elffd�d��Z�d�eldelfd�d��Z�Gd�d��d�e��Z�d
S)��N)
�defaultdict)
�is_dataclass)�date�datetime�time�	timedelta)
�Decimal)
�Enum)�IPv4Address�
IPv4Interface�IPv4Network�IPv6Address�
IPv6Interface�IPv6Network)
�Path)�
TYPE_CHECKING�Any�Callable�Dict�
ForwardRef�	FrozenSet�Generic�Iterable�List�Optional�Pattern�Sequence�Set�Tuple�Type�TypeVar�Union�cast)
�UUID)�	Annotated�Literal)
�MAPPING_LIKE_SHAPES�SHAPE_DEQUE�SHAPE_FROZENSET�
SHAPE_GENERIC�SHAPE_ITERABLE�
SHAPE_LIST�SHAPE_SEQUENCE�	SHAPE_SET�SHAPE_SINGLETON�SHAPE_TUPLE�SHAPE_TUPLE_ELLIPSIS�	FieldInfo�
ModelField)
�pydantic_encoder)�AnyUrl�EmailStr)�ConstrainedDecimal�ConstrainedFloat�ConstrainedFrozenSet�ConstrainedInt�ConstrainedList�ConstrainedSet�ConstrainedStr�SecretBytes�	SecretStr�StrictBytes�	StrictStr�conbytes�
condecimal�confloat�confrozenset�conint�conlist�conset�constr)	�all_literal_values�get_args�
get_origin�
get_sub_types�is_callable_type�is_literal_type�
is_namedtuple�is_none_type�is_union)�ROOT_KEY�	get_model�lenient_issubclass)
�	Dataclass�
�	BaseModelz#/definitions/z#/definitions/{model}rW�
modify_schema).N�field�field_schema�returncCsNd
dlm
}
||�
}t|j���
}d|vsd|vr!|||
d�
dS||�

dS)Nr
)
�	signaturerY�kwargs�
rY)�inspectr\�set�
parameters�keys)rXrYrZr\�sig�args�re�=/usr/local/lib/python3.10/dist-packages/pydantic/v1/schema.py�_apply_modify_schema`s


rgT)�by_alias�title�description�
ref_prefix�ref_template�modelsrUrhrirjrkrlc
Cs�d
d�|D�
}t|�
}t
|�
}i}	i}
|r||
d<|r||
d<|D]}t||
|||d�\}}
}|	�|
�

||}||	|<q!|	rC|	|
d<|
S)a�
    Process a list of models and generate a single JSON Schema with all of them defined in the ``definitions``
    top-level JSON key, including their sub-models.

    :param models: a list of models to include in the generated JSON Schema
    :param by_alias: generate the schemas using the aliases defined, if any
    :param title: title for the generated schema that includes the definitions
    :param description: description for the generated schema
    :param ref_prefix: the JSON Pointer prefix for schema references with ``$ref``, if None, will be set to the
      default of ``#/definitions/``. Update it if you want the schemas to reference the definitions somewhere
      else, e.g. for OpenAPI use ``#/components/schemas/``. The resulting generated schemas will still be at the
      top-level key ``definitions``, so you can extract them from there. But all the references will have the set
      prefix.
    :param ref_template: Use a ``string.format()`` template for ``$ref`` instead of a prefix. This can be useful
      for references that cannot be represented by ``ref_prefix`` such as a definition stored in another file. For
      a sibling json file in a ``/schemas`` directory use ``"/schemas/${model}.json#"``.
    :return: dict with the JSON Schema with a ``definitions`` top-level key including the schema definitions for
      the models and sub-models passed in ``models``.
    c
Ssg|]}
t|
�
�qSre)
rS)�.0�modelrererf�
<listcomp>�szschema.<locals>.<listcomp>rirj�rh�model_name_maprkrl�definitions)�get_flat_models_from_models�get_model_name_map�model_process_schema�update)rmrhrirjrkrl�clean_models�flat_modelsrrrs�
output_schemaro�m_schema�
m_definitions�m_nested_models�
model_namerererf�schemams.














�






rroc
Cslt|�
}t
|�
}t|�
}||}t||
|||d
�\}}}	||	vr+|||<t|||d�}|r4|�d|i
�

|S)aa
    Generate a JSON Schema for one model. With all the sub-models defined in the ``definitions`` top-level
    JSON key.

    :param model: a Pydantic model (a class that inherits from BaseModel)
    :param by_alias: generate the schemas using the aliases defined, if any
    :param ref_prefix: the JSON Pointer prefix for schema references with ``$ref``, if None, will be set to the
      default of ``#/definitions/``. Update it if you want the schemas to reference the definitions somewhere
      else, e.g. for OpenAPI use ``#/components/schemas/``. The resulting generated schemas will still be at the
      top-level key ``definitions``, so you can extract them from there. But all the references will have the set
      prefix.
    :param ref_template: Use a ``string.format()`` template for ``$ref`` instead of a prefix. This can be useful for
      references that cannot be represented by ``ref_prefix`` such as a definition stored in another file. For a
      sibling json file in a ``/schemas`` directory use ``"/schemas/${model}.json#"``.
    :return: dict with the JSON Schema for the passed ``model``
    rqFrs)rS�get_flat_models_from_modelrurv�get_schema_refrw)
rorhrkrlryrrr~r{r|�
nested_modelsrererf�model_schema�s





�



r�F�schema_overridescCs�i}|jj
st|jt�s|jj
p|j�
��d
d�|d<|jj
r!d}
|jjr-|jj|d<d}
|jsC|j	du
rCt
|j�
sCt|j	�
|d<d}
||
fS)N�
_�
 riTrj�default)
�
field_inforirT�type_r	�alias�replacerj�requiredr�rM�outer_type_�encode_default)rYr��schema_rererf�get_field_info_schema�s






r�)rhrkrl�known_modelsrrr�c
	Csnt|�
\}}t
|�
}|r|�|�

d
}t||
|||||pt�d�\}	}
}d|	vr-|	|
|fS|�|	�

||
|fS)a�
    Process a Pydantic field and return a tuple with a JSON Schema for it as the first item.
    Also return a dictionary of definitions with models as keys and their schemas as values. If the passed field
    is a model and has sub-models, and those sub-models don't have overrides (as ``title``, ``default``, etc), they
    will be included in the definitions and referenced in the schema instead of included recursively.

    :param field: a Pydantic ``ModelField``
    :param by_alias: use the defined alias (if any) in the returned schema
    :param model_name_map: used to generate the JSON Schema references to other models included in the definitions
    :param ref_prefix: the JSON Pointer prefix to use for references to other schemas, if None, the default of
      #/definitions/ will be used
    :param ref_template: Use a ``string.format()`` template for ``$ref`` instead of a prefix. This can be useful for
      references that cannot be represented by ``ref_prefix`` such as a definition stored in another file. For a
      sibling json file in a ``/schemas`` directory use ``"/schemas/${model}.json#"``.
    :param known_models: used to solve circular references
    :return: tuple of the schema for this field and additional definitions
    T�rhrrr�rkrlr��$ref)r��get_field_schema_validationsrw�field_type_schemar`)rYrhrrrkrlr��
sr��validation_schema�f_schema�
f_definitions�f_nested_modelsrererfrZ�s$










�




�
max_length�	maxLength�
min_length�	minLength�regex�pattern.�_str_types_attrs�gt�exclusiveMinimum�lt�exclusiveMaximum�ge�minimum�le�maximum�multiple_of�
multipleOf�_numeric_types_attrsc
Cs
i}
t|j
t�r|jjr|
�|jj�

|
St|j
ttf�r5tD]\}}}t	|j|d
�}t
||�r4||
|<qt|j
t�rYt|j
t
�sYtD]\}}}t	|j|d
�}t
||�rX||
|<qC|jd
u
rg|jjrg|j|
d<|jjrr|
�|jj�

t	|jdd
�}|r�t|||
�
|
S)z�
    Get the JSON Schema validation keywords for a ``field`` with an annotation of
    a Pydantic ``FieldInfo`` with validation arguments.
    N�const�__modify_schema__)rTr�r	r��extrarw�str�bytesr��getattr�
isinstance�
numeric_types�
issubclass�boolr�r�r�r�rg)rYr��	attr_name�
t�keyword�attrrXrererfr�!
s2






�





�








r��
unique_modelsc
Cs�i}
t�}|D]3}t
|j�
}||vrt|�
}||
|<q||
vr6|�|�

|
�|�
}||
t|�
<||
t|�
<q||
|<qd
d�|
��D�
S)a�

    Process a set of models and generate unique names for them to be used as keys in the JSON Schema
    definitions. By default the names are the same as the class name. But if two models in different Python
    modules have the same name (e.g. "users.Model" and "items.Model"), the generated names will be
    based on the Python module path for those conflicting models to prevent name collisions.

    :param unique_models: a Python set of models
    :return: dict mapping models to names
    c
Ssi|]\}
}||
�qSrere�rn�
k�
vrererf�
<dictcomp>Z
sz&get_model_name_map.<locals>.<dictcomp>)r`�normalize_name�__name__�get_long_model_name�add�pop�items)r��name_model_map�conflicting_namesror~�conflicting_modelrererfruB
s

















rucCsJ|
pt�}
t�}|�
|�

|
|O}
ttt|j���}|t||
d
�O}|S)a?
    Take a single ``model`` and generate a set with itself and all the sub-models in the tree. I.e. if you pass
    model ``Foo`` (subclass of Pydantic ``BaseModel``) as ``model``, and it has a field of type ``Bar`` (also
    subclass of ``BaseModel``) and that model ``Bar`` has a field of type ``Baz`` (also subclass of ``BaseModel``),
    the return value will be ``set([Foo, Bar, Baz])``.

    :param model: a Pydantic ``BaseModel`` subclass
    :param known_models: used to solve circular references
    :return: a set with the initial model and all its sub-models
    �
r�)r`r�r"rr2�
__fields__�values�get_flat_models_from_fields)ror�ry�fieldsrererfr�]
s







r�cCs�d
dlm
}
t�}|j}tt|dd�|�r|j}|jr+t||�s+|t|j|
d�O}|St||�r>||
v
r>|t	||
d�O}|St|t
�rH|�|�

|S)a�
    Take a single Pydantic ``ModelField`` (from a model) that could have been declared as a subclass of BaseModel
    (so, it could be a submodel), and generate a set with its model and all the sub-models in the tree.
    I.e. if you pass a field that was declared to be of type ``Foo`` (subclass of BaseModel) as ``field``, and that
    model ``Foo`` has a field of type ``Bar`` (also subclass of ``BaseModel``) and that model ``Bar`` has a field of
    type ``Baz`` (also subclass of ``BaseModel``), the return value will be ``set([Foo, Bar, Baz])``.

    :param field: a Pydantic ``ModelField``
    :param known_models: used to solve circular references
    :return: a set with the model used in the declaration for this field, if any, and all its sub-models
    r
rV�__pydantic_model__Nr�)�pydantic.v1.mainrWr`r�rTr�r��
sub_fieldsr�r�r	r�)rYr�rWry�
field_typerererf�get_flat_models_from_fieldq
s


�

�


r�r�cCs$t�}|D]
}|t
||
d
�O}q|S)a�
    Take a list of Pydantic  ``ModelField``s (from a model) that could have been declared as subclasses of ``BaseModel``
    (so, any of them could be a submodel), and generate a set with their models and all the sub-models in the tree.
    I.e. if you pass a the fields of a model ``Foo`` (subclass of ``BaseModel``) as ``fields``, and on of them has a
    field of type ``Bar`` (also subclass of ``BaseModel``) and that model ``Bar`` has a field of type ``Baz`` (also
    subclass of ``BaseModel``), the return value will be ``set([Foo, Bar, Baz])``.

    :param fields: a list of Pydantic ``ModelField``s
    :param known_models: used to solve circular references
    :return: a set with any model declared in the fields, and all their sub-models
    r�)r`r�)r�r�ryrYrererfr��
s


r�c
Cs t�}
|D]}|
t
|�
O}
q|
S)
a_

    Take a list of ``models`` and generate a set with them and all their sub-models in their trees. I.e. if you pass
    a list of two models, ``Foo`` and ``Bar``, both subclasses of Pydantic ``BaseModel`` as models, and ``Bar`` has
    a field of type ``Baz`` (also subclass of ``BaseModel``), the return value will be ``set([Foo, Bar, Baz])``.
    )r`r�)rmryrorererfrt�
s


rtc

Cs|j�d
|j
���dd
�S)N�__�
.)�
__module__�__qualname__r��
rorererfr��
s
r�)r�rkc
	Cs`d
dlm
}
i}t�}	|jtttttt	t
hvr?t||
||||d�\}
}}|�|�

|	�|�

d|
d�}
|jtthvr>d|
d<n�|jt
vr~dd	i
}
tt|j�}t|jd
d�}t||
||||d�\}
}}|�|�

|	�|�

|rwt�|�
|
i
|
d<|
r}|
|
d
<n�|jtks�|jtkr�t|j|�s�g}ttt|j�}|D]}t||
||||d�\}}}|�|�

|	�|�

|�|�

q�t|�
}|jtkr�|dkr�|d
nd|d�}d|g
i
}
n3d||d�}
|dkr�||
d<n$|jtthvs�J|j�
�
t||
|||||d�\}
}}|�|�

|	�|�

|j|jk�
r+|jtk�
r|j}n|j}t|dd�}|�
r+t|||
�
|
||	fS)a


    Used by ``field_schema()``, you probably should be using that function.

    Take a single ``field`` and generate the schema for its type only, not including additional
    information as title, etc. Also return additional schema definitions, from sub-models.
    r
rV�rhrrrkrlr��array��typer�T�uniqueItemsr��objectr�N�patternProperties�additionalProperties�
�allOf)r��minItems�maxItemsr�r�r�) r�rWr`�shaper+r0r,r-r(r*r'�field_singleton_schemarwr&r"r2�	key_fieldr�r�r<�_get_patternr/r)r�rr�r��append�lenr.r�rg)rYrhrrrlr�rkr�rWrsr��items_schemar�r�r�r�r��
sub_schemar��sf�	sf_schema�sf_definitions�sf_nested_models�sub_fields_len�all_of_schemasr�rXrererfr��
s�







�	





�






�










�




� 










�









�
�







�
	








r�)rhrkrlr�rYc
Cs�d
dlm
}m}
|pt�}t|t�r%ttt|�}t||d�}	|	it�fSttd|�}d|j	j
p3|ji
}	||�
}
|
r?|
|	d<|�|�

t
||
||||d�\}}}
|	�|�

|j	j}t|�
rrt||�
j�
dkrl||	�

n||	|�
n|	�|�

|	||
fS)	au

    Used by ``model_schema()``, you probably should be using that function.

    Take a single ``model`` and generate its schema. Also return additional schema definitions, from sub-models. The
    sub-models of the returned schema will be referenced, but their definitions will not be included in the schema. All
    the definitions are returned as the second value.
    r
)�getdocr\r^rWrirjr�r�)r_r�r\r`rTr	r"r�enum_process_schema�
__config__rir�r��model_type_schemarw�schema_extra�callabler�ra)rorhrrrkrlr�rYr�r\r��docr{r|r�r�rererfrv's8



















�








rv)
rkc
Cs
i}g}i}t�}	|j
��D]T\}
}zt||
||||d
�\}}
}Wnty:
}
z
t�|jt�
WYd}~qd}~w
w|�	|
�

|	�	|�

|
rV|||j
<|jrU|�|j
�

q|||
<|jrb|�|
�

qt
|vru|t
}|jjpq|j|d<nd|d�}|r�||d<|jjdkr�d|d	<|||	fS)
a)

    You probably should be using ``model_schema()``, this function is indirectly used by that function.

    Take a single ``model`` and generate the schema for its type only, not including additional
    information as title, etc. Also return additional schema definitions, from sub-models.
    r�Nrir�)r��
propertiesr��forbidFr�)r`r�r�rZ�	SkipField�warnings�warn�message�UserWarningrwr�r�r�rRr�rir�r�)rorhrrrlrkr�r�r�rsr�r��
fr�r�r��skip�
out_schemarererfr�YsN











�

��







�


�









r�r^�enumc

Cs`d
dl}|j
|�|jpd�
dd�ttt|�D�
d�}t||�
t|dd�}|r.t	||
|�
|S)z�
    Take a single `enum` and generate its schema.

    This is similar to the `model_process_schema` function, but applies to ``Enum`` objects.
    r
NzAn enumeration.c
Ssg|]}
|
j�qSre)
�value)rn�itemrererfrp��z'enum_process_schema.<locals>.<listcomp>)rirjr
r�)
r_r��cleandoc�__doc__r"rr	�add_field_type_to_schemar�rg)r
rYr_r�rXrererfr��s�
	

r�c

s�
tt
t|j�}i}t�}	t|�
d
kr t|d|
�|�
�|d�Si}
|jdu
}|r�|jdu
s0J�
i}|j�	�D]D\}
}t
|
t�rEt|
j
�
}
tt|j�
�
r_t|j�
}��
�fdd�|D�
||
<q7|j}t|d�rj|j}�|}t|�
�d�}|d	||
<q7|
r�|jn|j|d
�|
d<g}|D]8}t||
�|�
�|d�\}}}|�|�

|r�d|vr�|dd}|��dd
hkr�|�d�

|�|�

|	�|�

q�||
|r�d
n
d<|
||	fS)aA

    This function is indirectly used by ``field_schema()``, you probably should be using that function.

    Take a list of Pydantic ``ModelField`` from the declaration of a type with parameters, and generate their
    schema. I.e., fields used as "type parameters", like ``str`` and ``int`` in ``Tuple[str, int]``.
    r�r
r�Nc
s$i|]}
�|
t�|
�
�d��qS�
F)
r�)rn�	sub_model�rrrkrlrerfr��s�
��z5field_singleton_sub_fields_schema.<locals>.<dictcomp>r�Fr�)�propertyName�mapping�
discriminatorr��oneOf�anyOf)r"rr2r�r`r�r��discriminator_key�sub_fields_mappingr�r�r	r�r
rQrKr�rL�hasattrr�r��discriminator_aliasrwrbr�r�)rYrhrrrlr�rkr�r�rsr�r��field_has_discriminator�discriminator_models_refs�discriminator_value�	sub_field�
sub_models�sub_field_type�discriminator_model_name�discriminator_model_ref�sub_field_schemasr�r��sub_definitions�sub_nested_modelsrer
rf�!field_singleton_sub_fields_schema�sn










�










�






�








�
	







r!
�string�path)r��formatz	date-timerr�numberz
time-delta�ipv4network�ipv6network�
ipv4interface�
ipv6interface�ipv4�ipv6r��binary�boolean�integer�uuidr�r�r�)r�r�r��field_class_to_schemazjson-stringr�r�cCsDtD]\}}t
||�s||urturn
q|
�|�


d
Sqd
S)a

    Update the given `schema` with the type-specific metadata for the given `field_type`.

    This function looks through `field_class_to_schema` for a class that matches the given `field_type`,
    and then modifies the given `schema` with the information from that type.
    N)r0
rTrrw)r�r�r��t_schemarererfr	
$s"


��r	
�namecCs4|
r	d
|
|i
}nd
|j|d�
i
}|rd|g
i
S|S)Nr�r�r�)
r$
)r2
rkrlr��
schema_refrererfr�2s


r�c
	Cs�d
dlm
}
i}t�}	|j}
|jr(|jr|jjst|
|�s(t||
|||||d�S|
t	us;|
t
us;|
jtks;t
|
�
tur@i||	fSt|
�
rKddi
||	fSt|
�
rXtd|j�d��
�
i}|jdu
rh|jjrh|j|d	<t|
�
r�td
d�t|
�
D�
�
}tdd
�|D�
�
dkr�tt||�|
||||d�S|d
j}
t|�
|d<t|
|�
nft|
t�r�||
}
t||�\}}|�t|
|||��

t |
|d�||
<nCt!|
�
r�t"|
j#|
|||||d�^
}}t|d�$��
}|�d|t|�
t|�
d��

nt%|
d��
st|
|�
t&|
dd�}|�
rt'|||�
|�
r|||	fStt&|
dd�|��
r|
j#}
t(|
|��
rX||
}|
|v
�
rGt"|
|
|||||d�\}}}|�|�

|||<|	�|�

n|	�)|�

t||||�}|||	fSt*|
�
}|du
�
ro|�
sot+|
j,v�
ro|||	fSt-d|���
�
)z�
    This function is indirectly used by ``field_schema()``, you should probably be using that function.

    Take a single Pydantic ``ModelField``, and return its schema and any additional definitions from sub-models.
    r
rVr�r��nullz	Callable zC was excluded from schema since JSON schema has no equivalent type.Nr�c
ss$�|]
}
t|
t
�r|
jn
|
V
qdS�
N)r�r	r
)rn�
xrererf�	<genexpr>hs�"z)field_singleton_schema.<locals>.<genexpr>c
Ssh|]}
|
j�qSre)
�	__class__�rnr�rererf�	<setcomp>jr
z)field_singleton_schema.<locals>.<setcomp>r�r�r
r^)rhrrrkrlr�rYr�r�)r�r�r�r�r�r�z.Value not declarable with JSON Schema, field: ).r�rWr`r�r�r�r�rTr!
rr�r8
r rKr�rPrMr�r2
r�rN�tuplerIr�rZ�#multitypes_literal_field_for_schema�listr	
r	r�rwr�r�rOrvr�r�r
r�rgr�r�rJr�	__bases__�
ValueError)rYrhrrrlr�rkr�rWrsr�r�r�r��	enum_namer�r��
items_schemasrXr~r
r 
r3
rdrererfr�:s�


�
�
�






�&	

















�



















�	



��

















�
	








r�r�c
Csbtt
�
}|D]
}||j�|�

qd
d�|��D�
}t|
jtt|�
|
j	|
j
|
j|
j|
j
|
jd�S)z�
    To support `Literal` with values of different types, we split it into multiple `Literal` with same type
    e.g. `Literal['qwe', 'asd', 1, 2]` becomes `Union[Literal['qwe', 'asd'], Literal[1, 2]]`
    c
ss�|]	}
tt
|
�
V
qdSr5
)r%r;
)rn�same_type_valuesrererfr7
�s�z6multitypes_literal_field_for_schema.<locals>.<genexpr>)r2
r��class_validators�model_configr�r�r�r�)rr=
r8
r�r�r2r2
r!r;
rC
rD
r�r�r�r�)r�rY�literal_distinct_typesr��distinct_literalsrererfr<
�s











�r<
�dftc
Cs�d
dlm
}

t||
�st|�
rtdt|�
�}t|t�r$dd�|��D�
St|t�r,|j	St|t
ttf�r6|St|t
tf�rS|j}dd�|D�
}t|�
rO||�S||�
S|durYdSt|�
S)Nr
rVzdict[str, Any]c
Ssi|]\}
}t|
�
t|�
�qSre�
r�r�rererfr��sz"encode_default.<locals>.<dictcomp>c
ss�|]}
t|
�
V
qdSr5
rH
r9
rererfr7
���z!encode_default.<locals>.<genexpr>)r�rWr�rr"r3�dictr�r	r
�int�floatr�r=
r;
r8
rO)rG
rWr��seq_argsrererfr��s 














r��_map_types_constraint�
annotationr��
field_name�validate_assignmentcCsZ|
��}t
�}|rt||
�\}}|r|�d
�

||}|r+td|�dd�|�
�d��
�
|S)a=
    Get an annotation with validation implemented for numbers and strings based on the field_info.
    :param annotation: an annotation from a field specification, as ``str``, ``ConstrainedStr``
    :param field_info: an instance of FieldInfo, possibly with declarations for validations and JSON Schema
    :param field_name: name of the field for use in error messages
    :param validate_assignment: default False, flag for BaseModel Config value of validate_assignment
    :return: the same ``annotation`` if unmodified or a new annotation with validation in place
    �allow_mutationz
On field "z<" the following field constraints are set but not enforced: z, z\. 
For more details see https://docs.pydantic.dev/usage/schema/#unenforced-field-constraints)�get_constraintsr`�get_annotation_with_constraintsr�r?
�join)rO
r�rP
rQ
�constraints�used_constraints�unused_constraintsrererf�get_annotation_from_field_info�s









��rY
cs0t��d
t
dtt
f��
�fdd��
�
|�
�fS)a�

    Get an annotation with used constraints implemented for numbers and strings based on the field_info.

    :param annotation: an annotation from a field specification, as ``str``, ``ConstrainedStr``
    :param field_info: an instance of FieldInfo, possibly with declarations for validations and JSON Schema
    :return: the same ``annotation`` if unmodified or a new annotation along with the used constraints.
    r�r[c
	sbt��
st
�t�st�tttf�r�St��
}
|
du
r�t��
}t	d
d�|D�
�
r*�S|
t
ur4�|d�
St|
�
rEtt
�f
dd�|D�
�
St|
t�ro�
jdu
sY�
jdu
sY�
jdu
ro��hd�
�

t�|d�
�
j�
j�
jd�St|
t�r��
jdu
s~�
jdu
r���ddh�

t�|d�
�
j�
jd	�St|
t�r��
jdu
s��
jdu
r���ddh�

t�|d�
�
j�
jd	�StttttfD]}t|
|�r�|t
�f
d
d�|D�
�

Sq�t|
t�r�t|d�|d�
fSd}d}t
�t��
r�t�ttf��
rd}d
tdt tf�f
dd�}n~t�t!��
r-t�t"t#f��
s-d}t�t$��
r*d
tdt tf�f
dd�}nZt%}nWt�t&��
rLd}t�t'��
rId
tdt tf�f
dd�}n;t(}n8t�t)��
r�t�t*t+t,tttt-f��
s�d}t�t.��
rk|d7}t�t/��
ru|d7}t0�f
dd�t)D�
�
}t1|}|�
r���t2|�
�

dd��
f
dd�|D�
D�
}|�
r�t3t4dtf|�}|di|�
�
S�S)Nc
ss�|]}
t|
t
�V
qdSr5
)r�r�rn�
arererfr7
s�z>get_annotation_with_constraints.<locals>.go.<locals>.<genexpr>r
c
3��|]}
�|
�
V
qdSr5
rerZ
�
�gorerfr7
!rI
>�	max_items�	min_items�unique_items)r`
r_
ra
r`
r_
)r`
r_
c
3r\
r5
rerZ
r]
rerfr7
:rI
r�)r�r��kwr[c
�t�j
�f
|�Sr5
�r�r��
rb
�
r�rerf�constraint_funcE�
zDget_annotation_with_constraints.<locals>.go.<locals>.constraint_func)r�r�r�c
rc
r5
rd
re
rf
rerfrg
Lrh
c
rc
r5
rd
re
rf
rerfrg
Urh
)r�r�r�r�r�)
�
allow_inf_nan)�
max_digits�decimal_placesc
3s�|]
}
t�|
�r|
V
qdSr5
)
r�)rnr�rf
rerfr7
l��c
Ssi|]\}
}|du
r|
|�qSr5
re)rnr�r�rererfr�qs

�z?get_annotation_with_constraints.<locals>.go.<locals>.<dictcomp>c
3s�|]
}
|
t�|
�fV
qdSr5
)
r�)rnr�)
r�rerfr7
srl
.re)5rNr�rrTr:r;r8rKrJ�anyr$rQr!r;
r�rr`
r_
ra
rwrFrrGrrDrrrr�r>r=rrr�r5r4r@rHr�r?rAr�r9r7r6r�rL
r�nextrN
r`r"r)r��originrdr��attrsrg
�numeric_typer]�r�r^
rW
rf
rfr^
s����



















�






�


















��








�


z+get_annotation_with_constraints.<locals>.go)r`rr)rO
r�rerr
rfrT
skrT
c

Cst�
d
d|�S)zU
    Normalizes the given name. This can be applied to either a model *or* enum.
    z[^a-zA-Z0-9.\-_]r�)�re�sub)
r2
rererfr�~sr�c@s"eZ
dZd
Zdeddfdd�ZdS)r�z?
    Utility exception used to exclude fields from schema.
    r�r[NcCs
|
|_dSr5
)
r�)�selfr�rererf�__init__�s

zSkipField.__init__)r�r�r�r
r�rv
rerererfr��s
r�r

r5
)�rs
r��collectionsr�dataclassesrrrrr�decimalrr
r	�	ipaddressr
rrr
rr�pathlibr�typingrrrrrrrrrrrrrrrr r!r"r/
r#�typing_extensionsr$r%�pydantic.v1.fieldsr&r'r(r)r*r+r,r-r.r/r0r1r2�pydantic.v1.jsonr3�pydantic.v1.networksr4r5�pydantic.v1.typesr6r7r8r9r:r;r<r=r>r?r@rArBrCrDrErFrGrH�pydantic.v1.typingrIrJrKrLrMrNrOrPrQ�pydantic.v1.utilsrRrSrT�pydantic.v1.dataclassesrUr�rW�default_prefix�default_ref_template�TypeModelOrEnum�TypeModelSetr�rgr�rr�r�rZrK
rL
r�r�r��__annotations__r�r�rur�r�r�rtr�r�rvr�r�r!
r�rJ
r=
r;
r`�	frozensetr0
�json_schemer	
r�r�r<
r�rN
rY
rT
r��	Exceptionr�rerererf�<module>
s�







 

P
<
T
,




�
�

�
�



�
������

�7

�
����

�(&

�
��
���� 
�
3

.�



.�	! 

�
��
����� 	
�z


�
��
����� 	
�8�
��
���� 
�,6 
�
��
����� 	
�^




























$�
*
�
��
����� 	
�
(�
�
�
�
�
�&x