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

Fix documentation for IPvAny* schema mappings #433

Merged
merged 1 commit into from Mar 25, 2019
Merged

Fix documentation for IPvAny* schema mappings #433

merged 1 commit into from Mar 25, 2019

Conversation

sam-bristow
Copy link
Contributor

Change Summary

Update documentation for IPvAnyAddress, IPvAnyInterface and IPvAnyNetwork There was a minor typo - these types support both IPv4 and IPv6.

Related issue number

#333 (minor documentation fix-up)

Checklist

  • Unit tests for the changes exist
  • Tests pass on CI and coverage remains at 100%
  • Documentation reflects the changes where applicable
  • HISTORY.rst has been updated
    • if this is the first change since a release, please add a new section
    • include the issue number or this pull request number #<number>
    • include your github username @<whomever>

I think this was just a typo and these schemas support both IPv4 and IPv*6*.
@codecov
Copy link

codecov bot commented Mar 25, 2019

Codecov Report

Merging #433 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##           master   #433   +/-   ##
=====================================
  Coverage     100%   100%           
=====================================
  Files          14     14           
  Lines        2156   2156           
  Branches      426    426           
=====================================
  Hits         2156   2156

@samuelcolvin samuelcolvin merged commit 8e0bfa3 into pydantic:master Mar 25, 2019
@samuelcolvin
Copy link
Member

Thanks a lot, docs will be updated with the next release.

@sam-bristow sam-bristow deleted the patch-1 branch March 25, 2019 10:24
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.

None yet

2 participants