View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006060 | Taler | wallet (Android App) | public | 2020-01-22 19:57 | 2021-08-24 16:23 |
Reporter | grote | Assigned To | grote | ||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Target Version | 0.8 | Fixed in Version | 0.7.1 | ||
Summary | 0006060: Render pending events on main screen and top of history | ||||
Description | In most cases pending operations turn into history events quickly. Sometimes a pending operation indicates an error that requires attention from the user (i.e. when an operation failed because there is no internet connectivity) Some pending operations require something to happen *outside* the control of our software (for example when we are waiting for a bank transfer between the user's bank account and the exchange) The schema for pending operations is defined here: https://git.taler.net/wallet-core.git/tree/src/types/pending.ts | ||||
Tags | No tags attached. | ||||
|
Florian Dold, how should we handle pending operations that will never finish? Is there a way for the user to cancel/remove them? |
|
Every pending operation should have some "cancel" / "dismiss" action. What happens for this typically depends on the type of pending operation and would be implemented by wallet-core. When implementing the rendering, you should just assume that every pending operation has some "pendingOperationId" (just like history events have unique identifiers), and the wallet offers some "dismissPendingOperation" or maybe "cancelPendingOperation" API. Some types of pending operations might also offer different "actions", but dismissing them should be implemented first. For some types of pending operations the wallet would then automatically create a history event for the cancelled pending operation. |
|
> When implementing the rendering, you should just assume that every pending operation has some "pendingOperationId" (just like history events have unique identifiers), and the wallet offers some "dismissPendingOperation" or maybe "cancelPendingOperation" API. Do I need to assume their existence or are they already implemented somewhere, so I can actually use them? Or do you want me to just add a non-functional dismiss button everywhere. |
|
The pending operations are now only shown in developer mode. For users they have been replaced with transactions (past and *pending*) which abstract away internal details and surface only information that ordinary users should be able to understand. |
Date Modified | Username | Field | Change |
---|---|---|---|
2020-01-22 19:57 | grote | New Issue | |
2020-01-22 19:57 | grote | Status | new => assigned |
2020-01-22 19:57 | grote | Assigned To | => grote |
2020-01-22 19:59 | grote | Note Added: 0015294 | |
2020-01-22 20:47 | Florian Dold | Note Added: 0015295 | |
2020-01-23 17:00 | grote | Note Added: 0015297 | |
2020-05-25 15:19 | grote | Note Added: 0015956 | |
2020-05-25 15:19 | grote | Status | assigned => resolved |
2020-05-25 15:19 | grote | Resolution | open => fixed |
2020-05-25 15:19 | grote | Fixed in Version | => 0.7.1 |
2020-07-24 11:56 | Christian Grothoff | Target Version | => 0.8 |
2021-08-24 16:23 | Christian Grothoff | Status | resolved => closed |