View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010579 | Taler | documentation | public | 2025-11-10 22:12 | 2025-11-22 22:06 |
| Reporter | htgoebel | Assigned To | Christian Grothoff | 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 | text | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.0 | ||||
| Target Version | 1.2 | Fixed in Version | 1.2 | ||
| Summary | 0010579: trivial: RefundDetails.pending | ||||
| Description | The API documentaion for RefundDetails.pending says // Set to true if a refund is still available for the wallet for this payment. This sounds like one can *set*/*change* this value via the API. I suggest using the phrase "True if …" (as for CheckPaymentPaidResponse.refund_pending) or as a question "Is the refund still available for the wallet for this payment?" (as for CheckPaymentPaidResponse.refunded). | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-10 22:12 | htgoebel | New Issue | |
| 2025-11-11 11:47 | Christian Grothoff | Note Added: 0026376 | |
| 2025-11-11 11:47 | Christian Grothoff | Assigned To | => Christian Grothoff |
| 2025-11-11 11:47 | Christian Grothoff | Status | new => informing |
| 2025-11-11 11:47 | Christian Grothoff | Resolution | open => fixed |
| 2025-11-11 11:47 | Christian Grothoff | Fixed in Version | => 1.2 |
| 2025-11-11 11:47 | Christian Grothoff | Product Version | => 1.0 |
| 2025-11-11 11:47 | Christian Grothoff | Target Version | => 1.2 |
| 2025-11-22 22:06 | Christian Grothoff | Status | informing => closed |