[taler-docs] branch master updated: wallet API clarifications

[gnunet]

This is an automated email from the git hooks/post-receive script.

torsten-grote pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 07b15dd  wallet API clarifications
07b15dd is described below

commit 07b15dd14a52805b8c7c6f2621182c750e1dcc62
Author: Torsten Grote <address@hidden>
AuthorDate: Mon May 18 09:53:06 2020 -0300

    wallet API clarifications
---
 taler-wallet.rst | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/taler-wallet.rst b/taler-wallet.rst
index 82296e5..0308e57 100644
--- a/taler-wallet.rst
+++ b/taler-wallet.rst
@@ -106,17 +106,17 @@ Balances are the amounts of digital cash held by the 
wallet.
       currency?: string;
 
       // The total Amount that is currently available to be spent
-      // excluding amounts tied up in ongoing refresh operations. These are 
hidden from the user.
+      // including amounts tied up in ongoing refresh operations. These are 
hidden from the user.
       // If the user tries to spend coins locked up this way,
       // the wallet will give an error message different from "insufficient 
balance".
       available: Amount;
 
       // the total incoming amount that will be added to the available balance
-      // when all pending transactions succeed (excluding internal refreshes)
+      // when all pending transactions succeed (including internal refreshes)
       pendingIncoming: Amount;
 
       // the total outgoing amount that will be subtracted from the available 
balance
-      // when all pending transactions succeed (excluding internal refreshes)
+      // when all pending transactions succeed (including internal refreshes)
       pendingOutgoing: Amount;
 
       // true if the balance has pending transactions
@@ -151,7 +151,8 @@ Transactions are all operations or events that are 
affecting the balance.
       // a list of past and pending transactions sorted by pending, timestamp 
and transactionId.
       // In case two events are both pending and have the same timestamp,
       // they are sorted by the transactionId
-      // (lexically ascending and locale-independent comparison).
+      // (i.e. pending before non-pending transactions, newer before older
+      //  and if all equal transactionId lexically ascending).
       transactions: Transaction[];
     }
 

-- 
To stop receiving notification emails like this one, please contact
address@hidden.