You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attribute requirements implemented in pydantic with the Field class and coint, costr, etc. functions are a useful way to automatically verify that a payload provided by the user are exactly as we want.
Currently, for some attributes such as threshold, bit_length, version, etc. we don't provide such as there is a bug in our FastAPI version. See the discussion here: fastapi/fastapi#9140.
This bug is seen when a new documentation is generated.
As this bug is fixed in the latest FastAPI releases (at the time of writing this is 0.109.0) we can fix this bug and be free to add more requirements to our attributes.
To do this we need to close: #377 first.
For inspiration look at my commit before I realized there is an issue: MVrachev@8a00f5b
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
What is the task about?
Attribute requirements implemented in
pydantic
with theField
class andcoint
,costr
, etc. functions are a useful way to automatically verify that a payload provided by the user are exactly as we want.Currently, for some attributes such as
threshold
,bit_length
,version
, etc. we don't provide such as there is a bug in our FastAPI version. See the discussion here: fastapi/fastapi#9140.This bug is seen when a new documentation is generated.
As this bug is fixed in the latest FastAPI releases (at the time of writing this is
0.109.0
) we can fix this bug and be free to add more requirements to our attributes.To do this we need to close: #377 first.
For inspiration look at my commit before I realized there is an issue: MVrachev@8a00f5b
Code of Conduct
The text was updated successfully, but these errors were encountered: