From c265e7d019d445add2d2cfb7cfcbdeee059684d3 Mon Sep 17 00:00:00 2001 From: Florian Dold Date: Tue, 29 Mar 2022 13:47:32 +0200 Subject: wallet: make retries more robust and consistent --- packages/taler-wallet-core/src/operations/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'packages/taler-wallet-core/src/operations/README.md') diff --git a/packages/taler-wallet-core/src/operations/README.md b/packages/taler-wallet-core/src/operations/README.md index 426f2c553..9a2937c0c 100644 --- a/packages/taler-wallet-core/src/operations/README.md +++ b/packages/taler-wallet-core/src/operations/README.md @@ -17,7 +17,7 @@ Generally, the code to process a pending operation should first increment the retryInfo (and reset the lastError) and then process the operation. This way, it is impossble to forget incrementing the retryInfo. -For each retriable operation, there are usually `resetRetry`, `incrementRetry` and +For each retriable operation, there are usually `setupRetry`, `incrementRetry` and `reportError` operations. Note that this means that _during_ some operation, lastError will be cleared. The UI -- cgit v1.2.3