This repository has been archived by the owner on Feb 16, 2020. It is now read-only.
Fixing use of USDT with kraken #1381
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bugfix
getTicker doesn't respect the proper USDT pair type. Also it turn out that kraken accepts "USDTZUSD" and "USDTUSD" as the pair for the API query strings (always seems to return USDTZUSD though). Still an odd duck, but simplified the bug fix by letting me move it to a more global scope.
Fixed that stuff
We'll still need to validate the return format of getPortfolio since the wallet pairs were again formatted differently from the input pairs, another fix may yet be required for that after testing in live.
Should fix #1350