Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Trade updates (websocket) are in fact Aggregate Trade streams
See original GitHub issueCurrently the binance.websockets.trades function subscribes to the @aggTrade stream, while there is a separate @trade stream on the Binance API documentation.
It would be better if the current method was renamed binance.websockets.aggTrades and a new binance.websockets.trades was created, but I guess this would break the compatibility of this module.
I propose then implementing a binance.websockets.recentTrades method (to maintain this convention) on the current version and maybe reevaluating if it is worth breaking the compatibility on the next major version of this module.
What do you think about it? I can submit a PR.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
More importantly, we need to support the
(symbol)@tradewebsocket functionality https://github.com/binance-exchange/binance-official-api-docs/blob/master/web-socket-streams.md#trade-streamshttps://support.binance.com/hc/en-us/articles/360000713851-System-Upgrade-Extension