Closed chipshort closed 3 years ago
@chipshort Not sure why the build failed. It seems it was due some github instability as it passed now. Regarding your question, not aware of a better way of doing that. Thank you, to you and @vikulikov for futures account api.
Based on #101
I fixed some problems in the original PR and added the following:
The Transaction model has some values that are
string_or_float
, but also not always available. I added a separate serializer / deserializer for this:string_or_float_opt
. Is there a better way to do this?