Skip to content

Commit dac3782

Browse files
committed
doc: Correct AmountFromValue/ValueFromAmount names
1 parent fa64636 commit dac3782

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

doc/developer-notes.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -561,10 +561,10 @@ A few guidelines for introducing and reviewing new RPC interfaces:
561561
which is error prone, and it is easy to get things such as escaping wrong.
562562
JSON already supports nested data structures, no need to re-invent the wheel.
563563

564-
- *Exception*: AmountToValue can parse amounts as string. This was introduced because many JSON
564+
- *Exception*: AmountFromValue can parse amounts as string. This was introduced because many JSON
565565
parsers and formatters hard-code handling decimal numbers as floating point
566566
values, resulting in potential loss of precision. This is unacceptable for
567-
monetary values. **Always** use `AmountToValue` and `ValueToAmount` when
567+
monetary values. **Always** use `AmountFromValue` and `ValueFromAmount` when
568568
inputting or outputting monetary values. The only exceptions to this are
569569
`prioritisetransaction` and `getblocktemplate` because their interface
570570
is specified as-is in BIP22.

0 commit comments

Comments
 (0)