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
Adding deque to valid field types #1935
Conversation
cde07ab
to
1b64b31
Compare
Codecov Report
@@ Coverage Diff @@
## master #1935 +/- ##
=======================================
Coverage 99.90% 99.90%
=======================================
Files 21 21
Lines 4003 4021 +18
Branches 799 804 +5
=======================================
+ Hits 3999 4017 +18
Misses 3 3
Partials 1 1
Continue to review full report at Codecov.
|
efd3395
to
9cc3cbd
Compare
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.
Look good to me
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.
One tiny thing, otherwise this looks great.
you'll also need to resolve conflicts. |
9cc3cbd
to
a29a664
Compare
570834a
to
527f480
Compare
@samuelcolvin updated, thanks for the input 👍 this PR gave me a lot more context on how pydantic works, was fun to work on |
Co-authored-by: PrettyWood <em.jolibois@gmail.com>
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.
Thanks. LGTM!
Change Summary
Got bored so I PR'd an issue from @hongquan:
Adding deque as a valid sequence type for fields
Related issue number
Closes #1934
Checklist
changes/<pull request or issue id>-<github username>.md
file added describing change(see changes/README.md for details)