-
Notifications
You must be signed in to change notification settings - Fork 395
Client.write method breaking changes 2.0.0
#1089
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
Client.write method breaking changes 2.0.0
#1089
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1089 +/- ##
==========================================
+ Coverage 86.99% 87.09% +0.09%
==========================================
Files 64 64
Lines 3115 3146 +31
==========================================
+ Hits 2710 2740 +30
- Misses 405 406 +1
|
Client.write method breaking changes 2.0.0
|
@M0NsTeRRR in case you're interested in reviewing |
| value = dict.pop(member) | ||
| except KeyError: | ||
| if posvalue is not _sentinel: | ||
| return posvalue |
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.
Maybe its better to have only one return and do value = posvalue and for the next elif value = default for readability ?
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.
Maybe personal preference but I prefer the return for readability, otherwise I have to follow the rest of the flow to see where the value gets used again and/or returned.
|
LGTM (haven't time to test it) |
Implements:
Client.writemethod #1034 (v2 changes)Resolves #1079
This also adds a bunch of type hints and such, and some additional test coverage.