fetchTicker() en masse incorrect treatment of base/quote volume
See original GitHub issueLooks like a result of copypaste which is spread over all exchanges.
I don’t think it wise to check with all the API docs for all exchanges to determine if they indeed return base or quote. I believe it would be quite safe to assume that if exchange provides only one volume than treat it as baseVolume
rather than quoteVolume
.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
What Is a Currency Pair? Major, Minor, and Exotic Examples
All currency pairs are categorized according to the volume that is traded on a daily basis for a pair. The currencies that trade...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Actually, I just ran a simple smoke test on 1.9.59 (just
BTC/USD
pair):What I’ve got is:
Those which have
undefined
asbaseVolume
and up to five digits asquoteVolume
are just leftovers after the split.Some figures seem to be just insane, in particular:
Looks like they return ticket info although they don’t quote in USD at all.
Ok, I fixed most of those bugs, but there may still be some issues with volumes, I’ll test and debug further to bring it all to a consistent return. The bug was caused by the fact, that we had only one volume for the tickers initially, and then it was split into base/quote with some errors left over. Hope to fix them all. Thx again for your help! I’m closing this for now, if you don’t mind. Feel free to reopen it if needed. I’ll continue the work on this anyway.