Skip to content
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

Merged
merged 7 commits into from Oct 25, 2020

Conversation

wozniakty
Copy link
Contributor

@wozniakty wozniakty commented Sep 19, 2020

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

  • Unit tests for the changes exist
  • Tests pass on CI and coverage remains at 100%
  • Documentation reflects the changes where applicable
  • changes/<pull request or issue id>-<github username>.md file added describing change
    (see changes/README.md for details)

@wozniakty wozniakty force-pushed the field-type-deque branch 3 times, most recently from cde07ab to 1b64b31 Compare September 19, 2020 10:29
@codecov
Copy link

codecov bot commented Sep 19, 2020

Codecov Report

Merging #1935 into master will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           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           
Impacted Files Coverage Δ
pydantic/errors.py 100.00% <100.00%> (ø)
pydantic/fields.py 100.00% <100.00%> (ø)
pydantic/json.py 100.00% <100.00%> (ø)
pydantic/utils.py 100.00% <100.00%> (ø)
pydantic/validators.py 100.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d14731f...eb467ee. Read the comment docs.

@wozniakty wozniakty force-pushed the field-type-deque branch 2 times, most recently from efd3395 to 9cc3cbd Compare September 19, 2020 10:41
Copy link

@hongquan hongquan left a 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

Copy link
Member

@samuelcolvin samuelcolvin left a 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.

docs/usage/types.md Show resolved Hide resolved
@samuelcolvin
Copy link
Member

you'll also need to resolve conflicts.

@wozniakty
Copy link
Contributor Author

@samuelcolvin updated, thanks for the input 👍 this PR gave me a lot more context on how pydantic works, was fun to work on

docs/usage/types.md Outdated Show resolved Hide resolved
Co-authored-by: PrettyWood <em.jolibois@gmail.com>
Copy link
Member

@PrettyWood PrettyWood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. LGTM!

@samuelcolvin samuelcolvin merged commit 3e4c1b5 into pydantic:master Oct 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Accept deque as sequence-like input data type
4 participants