Closed
Conversation
- Fix balance field description in NewAddressInfo common structure
- Update task::get_new_address::status response examples with correct balance format
- Update task::scan_for_new_addresses::status response examples with correct balance format
- Add examples showing both single-token and multi-token platform responses
- Balance field is a map/object with token tickers as keys, not a simple BalanceInfo object
The balance structure should be:
{
"[TOKEN_TICKER]": {
"spendable": "amount",
"unspendable": "amount"
}
}
Addresses issue where documentation showed incorrect balance format that didn't match actual API responses.
…cture-dev fix: correct NewAddressInfo balance structure in dev branch API documentation
Kdf/import/common structures
Contributor
Author
|
closing in favor of #563 |
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
NewAddressInfoand adds some examples.Much work has already been done towards improving the common structures in #511
To reduce future merge conflicts (and the size of that PR!) I'll migrate those changes into this branch.