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: use correct type annotation #114

Merged
merged 1 commit into from
Jan 15, 2023
Merged

Conversation

FelixTheC
Copy link
Owner

Fix type annotation in typed_namedtuple

@FelixTheC FelixTheC added the bug Something isn't working label Jan 15, 2023
@FelixTheC FelixTheC self-assigned this Jan 15, 2023
@codecov
Copy link

codecov bot commented Jan 15, 2023

Codecov Report

Merging #114 (0753a4b) into py_3_10 (19ad941) will decrease coverage by 0.05%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           py_3_10     #114      +/-   ##
===========================================
- Coverage    89.82%   89.77%   -0.06%     
===========================================
  Files           27       27              
  Lines         3107     3089      -18     
===========================================
- Hits          2791     2773      -18     
  Misses         316      316              
Impacted Files Coverage Δ
strongtyping/type_namedtuple.py 94.00% <ø> (ø)
strongtyping/tests/test_typed_namedtuple.py 99.13% <100.00%> (-0.12%) ⬇️

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@FelixTheC FelixTheC merged commit dc33837 into py_3_10 Jan 15, 2023
@FelixTheC FelixTheC deleted the hotfix_typed_namedtuple branch January 15, 2023 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant