View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011794 | Taler | wallet-core | public | 2026-09-13 12:46 | 2026-09-13 12:46 |
| Reporter | Florian Dold | Assigned To | Florian Dold | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | implementing | Resolution | open | ||
| Target Version | 1.7 | ||||
| Summary | 0011794: wallet-core should have observation helpers for domain views, starting with transactions | ||||
| Description | Right now the UIs need to understand a lot of notifications and make various separate requests to update their UI state. To simplify this, we should introduce helpers to observe transactions (or other domain models) that give the UI consistent snapshots of their state. For example: { "id": 101, "operation": "observePayment", "args": { "transactionId": "txn:payment:example", "observationId": "payment-screen-17" } } Now, a notification when a payment becomes affordabe: { "type": "notification", "payload": { "type": "payment-snapshot", "observationId": "payment-screen-17", "revision": 1, "payment": { "transactionId": "txn:payment:example", "txState": { "major": "dialog", "minor": "proposed" }, "choices": [ { "choiceIndex": 0, "status": "insufficient-balance", "amountRaw": "EUR:5" } ] } } } | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-09-13 12:46 | Florian Dold | New Issue | |
| 2026-09-13 12:46 | Florian Dold | Assigned To | => Florian Dold |
| 2026-09-13 12:46 | Florian Dold | Status | new => assigned |
| 2026-11-03 07:21 | Status | assigned => implementing |