You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 29, 2022. It is now read-only.
Is there any specific reason to use int instead of float64 for Size and FilledSize under TriggerHistory struct.
JSON decoding is failing since its not a float with below error
rest.Response.Error: Result: orders.ResponseForOrderTriggerHistories: orders.TriggerHistory.Size: assertInteger: can not decode float as int, error found in #10 byte of ...|0,"size":1.0,"status|..., bigger context ...|t","orderPrice":null,"triggerPrice":100.0,"size":1.0,"status":"cancelled","createdAt":"2021-08-17T01|...
The text was updated successfully, but these errors were encountered:
Hello There,
Thanks for the amazing library.
Is there any specific reason to use int instead of float64 for Size and FilledSize under TriggerHistory struct.
JSON decoding is failing since its not a float with below error
rest.Response.Error: Result: orders.ResponseForOrderTriggerHistories: orders.TriggerHistory.Size: assertInteger: can not decode float as int, error found in #10 byte of ...|0,"size":1.0,"status|..., bigger context ...|t","orderPrice":null,"triggerPrice":100.0,"size":1.0,"status":"cancelled","createdAt":"2021-08-17T01|...
The text was updated successfully, but these errors were encountered: