search

gateio / gatews

Gate Websocket V4 SDK
89 stars 35 forks source link

Delivery Futures - No mapping possible due to missing information in response #18

Closed ChristianCoenen closed 2 years ago

ChristianCoenen commented 2 years ago

Currently, only the WebSocket servers for Spot and Perpetual Futures return an ID when subscribing to a channel (as stated in the gateio documentation).

Screenshot 2021-12-12 at 11 44 19

However, the Delivery Futures WebSocket server does not send back an ID or the payload in the subscribe response => no mapping possible. This makes it impossible to properly create automated trading tools for the delivery futures on gateio!

Analyzing the code, it looks to me that currently an old implementation is used for the Delivery Futures. Is it planned to be migrated into this codebase in the near future? If not, I would recommend a small update to add the request-id to the response for subscribe and unsubscribe events.

Please let me know if I should open the issue in the old repository as well.

revilwang commented 2 years ago

Yes, the delivery futures currently does not send back the ID in request payload. We'll add this feature, when it's finished, I'll report here.

revilwang commented 2 years ago

Feature has been supported (though really a bit late)