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
Currently get_decimals takes a 3rd argument for future DataType corresponding to the expiration timestamp, this shouldn't be necessary. We can make the assumption that all expiries have the same decimals.
The text was updated successfully, but these errors were encountered:
whatever the expiration_timestamp provided, the decimals that will be retrieved will be the one associated with the pair id for the given future. While calling get_decimals, you can just provide the pair_id for the future entry and set the expiration_timestamp to 0 and it will work fine. I can eventually change the code to
in order to make the code clearer, but it will not change the input argument. We can possibly change the input argument in order to remove the DataType parameter, but we will still have to provide the pair id and the type of data (spot, future...)
Currently
get_decimals
takes a 3rd argument for futureDataType
corresponding to the expiration timestamp, this shouldn't be necessary. We can make the assumption that all expiries have the same decimals.The text was updated successfully, but these errors were encountered: