diff options
| author | Florian Dold <florian@dold.me> | 2022-03-29 13:47:32 +0200 |
|---|---|---|
| committer | Florian Dold <florian@dold.me> | 2022-03-29 13:48:51 +0200 |
| commit | c265e7d019d445add2d2cfb7cfcbdeee059684d3 (patch) | |
| tree | 6904e9cdb723992728ed511103be65094ca50034 /packages/taler-wallet-core/src/operations/README.md | |
| parent | be489b6b3ea4214f546dfc33d6bb0f39ce82b5ab (diff) | |
| download | wallet-core-c265e7d019d445add2d2cfb7cfcbdeee059684d3.tar.xz | |
wallet: make retries more robust and consistent
Diffstat (limited to 'packages/taler-wallet-core/src/operations/README.md')
| -rw-r--r-- | packages/taler-wallet-core/src/operations/README.md | 2 |
1 files changed, 1 insertions, 1 deletions
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 `reset<Op>Retry`, `increment<Op>Retry` and +For each retriable operation, there are usually `setup<Op>Retry`, `increment<Op>Retry` and `report<Op>Error` operations. Note that this means that _during_ some operation, lastError will be cleared. The UI |