Change TradeInfo proto's tradePrice & tradeVolume fields to string [#5] #6062
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
This commit adds comments to grpc.proto to be pulled into a new API reference doc. Some of the comments highlight issues to be resolved in following PRs. The main focus is on documenting gRPC Offers service definitions in grpc.proto: - Comment each field in the Offers service's messages. - Add TODO comments about fixing field defs with usability & consistency problems. Other API reference doc related changes to grpc.proto: - Comment each gRPC service's rpc method definitions, however briefly. - Improve some existing rpc method comments.
We will consider each problematic number field one at a time. Note: changing field types in following commits will break the API's backward compatibility, but devs agree it's OK since it is still in beta.
The new console output formatting (tbl) api is working, and the deprecated classes just add maintenance work. Update affected test cases.
Much less ambiguous field value at cost of breaking backward compat in API.
…ring triggerPrice`.
Some minor refactoring included.
Quite a bit of refactoring. A lot of number-string formatting was removed.
This was referenced Feb 20, 2022
ripcurlx
approved these changes
Feb 28, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
As longs, they created confusion, and extra client side code for handling display of trade prices and volumes.
Java/Python API client devs will not have to try to figure out how long values are representing fractional fiat/altcoin prices and volumes.
Just changing volume or price field to string would leave the PR in an incomplete, messy state, so changed both in same PR.
Summary:
Change
TradeInfo.proto'stradePrice&tradeVolumefields from long to string.Adjust
core.api.model.proto wrappers to price & volume type change.Adjust
clitoTradeInfo.proto's price & volume type change. Quite a bit of refactoring inclimodule. A lot of number-string formatting was removed.Adjust apitest cases to
TradeInfo.proto's price & volume type change.XMR amounts/volumes are now shown with a precision of 8 in the CLI console.
Based on branch
4-change-grpc-proto-volume-to-string, PR #6060