mirror of
https://github.com/dashpay/dash.git
synced 2024-12-24 19:42:46 +01:00
doc: Correct AmountFromValue/ValueFromAmount names
This commit is contained in:
parent
fa64636948
commit
dac37823d4
@ -561,10 +561,10 @@ A few guidelines for introducing and reviewing new RPC interfaces:
|
||||
which is error prone, and it is easy to get things such as escaping wrong.
|
||||
JSON already supports nested data structures, no need to re-invent the wheel.
|
||||
|
||||
- *Exception*: AmountToValue can parse amounts as string. This was introduced because many JSON
|
||||
- *Exception*: AmountFromValue can parse amounts as string. This was introduced because many JSON
|
||||
parsers and formatters hard-code handling decimal numbers as floating point
|
||||
values, resulting in potential loss of precision. This is unacceptable for
|
||||
monetary values. **Always** use `AmountToValue` and `ValueToAmount` when
|
||||
monetary values. **Always** use `AmountFromValue` and `ValueFromAmount` when
|
||||
inputting or outputting monetary values. The only exceptions to this are
|
||||
`prioritisetransaction` and `getblocktemplate` because their interface
|
||||
is specified as-is in BIP22.
|
||||
|
Loading…
Reference in New Issue
Block a user