View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006086 | Taler | bank API (C) | public | 2020-02-10 18:41 | 2020-03-31 14:04 |
| Reporter | grote | Assigned To | grote | 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 | feature | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | git (master) | ||||
| Target Version | 0.7.0 | Fixed in Version | 0.7.0 | ||
| Summary | 0006086: Provide bank API endpoint to get current account balance | ||||
| Description | One way of doing this could be to add some fields to the basic JSON response to include the beginning/ending balances around the history that is being returned. For the cashier app, only the current balance is needed. | ||||
| Tags | No tags attached. | ||||
| I have proposed (but not implemented!) an API for this in a757d05..02507a8 (docs.git). Torsten: please let me know if the API is clear and will suffice in your opinion. Marcello/Florian: please make sure this is implementable for libeufin/Nexus. | |
| Looking at this change, I would either choose the incoming or the outgoing history endpoint and then do (current_incoming - total_outgoing_end) or (total_incoming_end - current_outgoing) to calculate the current balance, right? Unrelated to the issue at hand: The change doesn't make clear anymore that outgoing_transactions and incoming_transactions is an array. | |
| I fixed the array issue, but then Florian now convinced me that this is the 'wrong' place to do this. So most of my change will be reverted. We discussed that likely Marcello will write the 'right' API (ideally spec+implementation). Stay tuned... | |
| This seems to have been implemented. Can we close this ticket? | |
| If it works for you, sure. Except 'resolve' is the right state until we made the release. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-02-10 18:41 | grote | New Issue | |
| 2020-02-10 18:41 | grote | Status | new => assigned |
| 2020-02-10 18:41 | grote | Assigned To | => Christian Grothoff |
| 2020-02-10 22:49 | Christian Grothoff | Note Added: 0015340 | |
| 2020-02-10 22:49 | Christian Grothoff | Assigned To | Christian Grothoff => grote |
| 2020-02-10 22:49 | Christian Grothoff | Status | assigned => feedback |
| 2020-02-10 22:49 | Christian Grothoff | Product Version | => git (master) |
| 2020-02-10 22:49 | Christian Grothoff | Target Version | => 0.7.1 |
| 2020-02-10 22:49 | Christian Grothoff | Note Edited: 0015340 | |
| 2020-02-10 23:15 | grote | Note Added: 0015343 | |
| 2020-02-11 21:25 | Christian Grothoff | Note Added: 0015348 | |
| 2020-03-06 16:57 | grote | Note Added: 0015434 | |
| 2020-03-06 20:23 | Christian Grothoff | Note Added: 0015435 | |
| 2020-03-09 18:20 | grote | Status | feedback => informing |
| 2020-03-09 18:20 | grote | Resolution | open => fixed |
| 2020-03-17 01:08 | Christian Grothoff | Fixed in Version | => 0.7.0 |
| 2020-03-17 01:08 | Christian Grothoff | Target Version | 0.7.1 => 0.7.0 |
| 2020-03-31 14:04 | Christian Grothoff | Status | informing => closed |