View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010614 | Taler | merchant backend | public | 2025-11-14 22:42 | 2025-11-15 00:49 |
| Reporter | htgoebel | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | won't fix | ||
| Product Version | 1.0 | ||||
| Target Version | 1.2 | Fixed in Version | 1.2 | ||
| Summary | 0010614: Inconsitent naming of data in Responses | ||||
| Description | The same data has different names in different Response types. E.g. OrderHistoryEntry.timestamp vs. CheckPaymentUnpaidResponse.creation_time. Expected: data with same meaning has same name in all data types. | ||||
| Tags | No tags attached. | ||||
|
|
In principle, you are right. But we have seen things break very badly from renaming fields, and I don't see us doing any major rename fests at any point in the predictable future, simply because that's a LOT of (potential) breakage causing a lot of work for limited gain. Plus, we just don't have the resources of keeping a dozen developers from introducing new inconsistencies. So sure, we should try when introducing, but I don't see us doing a major push to fix these anytime soon. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-11-14 22:42 | htgoebel | New Issue | |
| 2025-11-15 00:49 | Christian Grothoff | Status | new => closed |
| 2025-11-15 00:49 | Christian Grothoff | Resolution | open => won't fix |
| 2025-11-15 00:49 | Christian Grothoff | Product Version | => 1.0 |
| 2025-11-15 00:49 | Christian Grothoff | Fixed in Version | => 1.2 |
| 2025-11-15 00:49 | Christian Grothoff | Target Version | => 1.2 |
| 2025-11-15 00:49 | Christian Grothoff | Note Added: 0026454 |
