-
Notifications
You must be signed in to change notification settings - Fork 21
fix(python): update deserialization templates and typing issues #3780
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✔️ Code generated!
📊 Benchmark resultsBenchmarks performed on the method using a mock server, the results might not reflect the real-world performance.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
spec correctness >>> pydantic shit
@@ -0,0 +1,6 @@ | |||
argcomplete==3.5.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is the CI deleting this file everytime ? I see it everywhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it doesn't push it on the CI but I can't understand why ahaha
… (generated) [skip ci] Co-authored-by: Clément Vannicatte <[email protected]>
…rated) algolia/api-clients-automation#3780 Co-authored-by: algolia-bot <[email protected]> Co-authored-by: Clément Vannicatte <[email protected]>
🧭 What and Why
🎟 JIRA Ticket: https://algolia.atlassian.net/browse/DI-2787 https://algolia.atlassian.net/browse/DI-2915
Changes included:
supersede #3758
this pr updates the python template in order to better leverage pydantic and improve usage in general:
extra
fields for native additional properties supportto_dict
unwrap in tests rather than the model-level one, this allows us to have a more concrete usage, as it's unlikely that users will iterate over the fields to parse them