View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007275 | Taler | specification | public | 2022-07-05 13:12 | 2024-01-12 14:03 |
| Reporter | Christian Grothoff | Assigned To | Christian Grothoff | ||
| Priority | immediate | Severity | tweak | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Target Version | 0.9.3 | Fixed in Version | 0.9.3 | ||
| Summary | 0007275: debit_account / credit_account are highly redundant in bank-api transaction histories | ||||
| Description | When requesting a credit/debit history, the affected account is repeated in every single entry of the account history. This wastes bandwidth and computation time (parsing!) and is simply inelegant. We should refactor the API to only return the main account the credit/debit histories are for ONCE (or zero? after all, the client should know what it requested?), and certainly not for every transaction. Note: this change needs to be coordinated across all bank clients and implementations. | ||||
| Tags | No tags attached. | ||||
| related to | 0007300 | closed | Florian Dold | Taler bank access API does not follow conventions |
|
|
Let's fix this together with 0007300. |
|
|
Fixed in docs.git. |
|
|
5adf8fab..d289bb87 changes merchant.git (Anastasis/merchant facade) to use the non-redundant API style. |
|
|
exchange.git::f7de830b..fd6a1d1a modifies the exchange bank and fakebank to use the new non-redundant style. |
|
|
libeufin.git at 7ccac24e29bd825ac2e0e721226ccabde6d947cc got changed after this bug. Setting as feedback until tests from the exchange code-base confirm the correctness. |
|
|
Can't yet confirm, as all tests were migrated to fakebank and/or are commented out because they were failing for a while. Will investigate. |
|
|
Solved at least in fakebank, libeufin will have it fixed once 0.9.3 is out. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2022-07-05 13:12 | Christian Grothoff | New Issue | |
| 2022-07-05 13:12 | Christian Grothoff | Status | new => assigned |
| 2022-07-05 13:12 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2022-07-05 14:55 | Christian Grothoff | Assigned To | Christian Grothoff => MS |
| 2022-11-02 15:32 | Christian Grothoff | Priority | urgent => normal |
| 2022-12-20 19:38 | Christian Grothoff | Target Version | => 0.11 |
| 2023-09-03 17:35 | Christian Grothoff | Target Version | 0.11 => 0.9.3 |
| 2023-09-03 17:36 | Christian Grothoff | Note Added: 0020485 | |
| 2023-09-03 17:36 | Christian Grothoff | Relationship added | related to 0007300 |
| 2023-09-03 17:55 | Christian Grothoff | Note Added: 0020486 | |
| 2023-09-03 17:59 | Christian Grothoff | Note Added: 0020487 | |
| 2023-09-03 18:00 | Christian Grothoff | Note Added: 0020488 | |
| 2023-09-03 18:00 | Christian Grothoff | Priority | normal => immediate |
| 2023-09-05 09:35 | MS | Note Added: 0020494 | |
| 2023-09-05 09:35 | MS | Status | assigned => feedback |
| 2023-09-05 14:58 | Christian Grothoff | Assigned To | MS => Christian Grothoff |
| 2023-09-05 14:58 | Christian Grothoff | Note Added: 0020502 | |
| 2023-09-23 14:59 | Christian Grothoff | Status | feedback => resolved |
| 2023-09-23 14:59 | Christian Grothoff | Resolution | open => fixed |
| 2023-09-23 14:59 | Christian Grothoff | Fixed in Version | => 0.9.3 |
| 2023-09-23 14:59 | Christian Grothoff | Note Added: 0020524 | |
| 2023-09-23 15:09 | Christian Grothoff | Status | resolved => closed |
| 2024-01-12 14:03 | Christian Grothoff | Category | exchange API (HTTP specification) => specification |
