-
Notifications
You must be signed in to change notification settings - Fork 6
[FLAPI-2083] Fix various models type hints when maybe parsing #54
Conversation
c8ed337
to
d37cca5
Compare
Order
modelOrder
, Offer
models type hints
d37cca5
to
24b8e52
Compare
Order
, Offer
models type hints24b8e52
to
d351722
Compare
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.
LGTM. 👍
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.
🤔
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.
Some of these changes have broken the implementation – check the integration tests in examples/
for pointers to where.
@sgerrand: I'll go through them today. |
Thanks Jesse! |
1091597
to
508de6f
Compare
I'm pointing out the obvious but
|
Yup, I'm working on those atm. I've got them recorded in the TODO list in the description. Thanks for making sure it's not missed though! I think I've found some pre-existing bugs through refactoring this. 😬 |
Nice – that's good thing! |
f68be40
to
e5e1d2c
Compare
@sgerrand: This is ready for review now. |
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.
LGTM. 👍
We don't actuall serialise `Payment`s at the moment.
e5e1d2c
to
ca6005f
Compare
Fix Order model type hints
By (possibly) setting the
value
varaible to a non-iterable type, we get warnings. Instead, explicitly continue on once we maybe parse astr
type. We wouldn't want to iterate over astr
.We don't serialise
Payment
s forOrder
s so I've removed them from the appropriate fixtures.TODO