[48] refactor to use free functions#49
Conversation
|
|
|
yes, sorry - this builds on #44 |
6caa135 to
af5bee8
Compare
|
coverage at 91% |
aade427 to
e34111b
Compare
e34111b to
a729cd4
Compare
|
rebased, single commit. ready for review. |
the two lines in data_objects.py are reading and writing with a ticket. not sure how to do that. |
korydraughn
left a comment
There was a problem hiding this comment.
Looks good overall.
The main thing is in how errors are checked (string comparisons) and checking of HTTP status codes.
08aa01d to
40a54e2
Compare
|
only one line untested - not sure how to generate that error text at the moment. |
65ec4a0 to
a2be019
Compare
alanking
left a comment
There was a problem hiding this comment.
Given the size of this change and the fact that this hasn't been released yet, are there any areas in particular that you feel need special attention for review?
|
At this point, after the refactor to free functions, module naming, and lots of coverage work and test cleanup... I think there is only the one discussion about multipart/form-data that remains - #49 (comment) Everything else feels pretty clean, and any fixups could happen after an initial release. |
449404f to
fae7f2f
Compare
|
There's one unresolved comment left? |
fae7f2f to
bc88f58
Compare
|
comment resolved. yes, all passing. |
bc88f58 to
8d01e54
Compare
|
all pounded. |
currently a single commit beyond branch 36.m, will rebase once that is merged.
all tests pass