diff options
| author | Florian Dold <florian@dold.me> | 2022-10-14 18:50:38 +0200 |
|---|---|---|
| committer | Florian Dold <florian@dold.me> | 2022-10-14 22:10:10 +0200 |
| commit | 398e79d0d6b649d8921ffffa4d0be8775c15626e (patch) | |
| tree | b4ac967a867041f440ea50e9460efd7209cc5f55 | |
| parent | b011c8a32ed478807737b96a9d7fc4e0ff085bdb (diff) | |
-remove obsolete README section
| -rw-r--r-- | packages/taler-wallet-core/src/operations/README.md | 19 |
1 files changed, 0 insertions, 19 deletions
diff --git a/packages/taler-wallet-core/src/operations/README.md b/packages/taler-wallet-core/src/operations/README.md index 9a2937c0c..a40349d37 100644 --- a/packages/taler-wallet-core/src/operations/README.md +++ b/packages/taler-wallet-core/src/operations/README.md @@ -5,22 +5,3 @@ This folder contains the implementations for all wallet operations that operate To avoid cyclic dependencies, these files must **not** reference each other. Instead, other operations should only be accessed via injected dependencies. Avoiding cyclic dependencies is important for module bundlers. - -## Retries - -Many operations in the wallet are automatically retried when they fail or when the wallet -is still waiting for some external condition (such as a wire transfer to the exchange). - -Retries are generally controlled by a "retryInfo" field in the corresponding database record. This field is set to undefined when no retry should be scheduled. - -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 `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 -should accommodate for this. - -It would be possible to store a list of last errors, but we currently don't do that. |