zmievsa/pydantic-duality

Automatically and lazily generate three versions of your pydantic models: one with Extra.forbid, one with Extra.ignore, and one with all fields optional

Hi there, my name is Stanislav Zmiev 👋

• I am a Platform Engineer with an extensive experience in devtools and backend Development
• I have done a fair share of frontend, mobile, DevOps, and lower level stuff in my spare time
• I have built numerous open source projects over the years, most of which can be found on my GitHub page
• My passion is creating and combining development tools to provide programmers with the best possible support while coding. To increase value without needing to increase the team size
• In my spare time, I contribute to open source and participate in developer meetups and conferences. Over the years I have contributed code to:
  • CPython
  • typeshed
  • tortoise-orm
  • ideas
  • pygount
  • inflect

... any many smaller projects!

pydantic-duality's Issues

Split documentation into multiple pages

Currently, all docs live on the same page which can get quite uncomfortable to use and limits us in terms of documentation's structure. Splitting it into multiple pages and adding them to sidebar might make it much nicer.

Add a note into readme about why we needed to use extra.ignore for responses

Add a test case for A.__request__ == A

Custom request/response schema class names

Im using FastAPI and I need to name my request and response schemas in a certain way

It would be cool if I can define either prefix or/and suffix of a request/response schema or define the class name (because FastApi uses class name as a schema name in openapi) on schema generation