View Issue Details

IDProjectCategoryView StatusLast Update
0010614Talermerchant backendpublic2025-11-14 23:49
Reporterhtgoebel Assigned ToResolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionwon't fix 
Product Version1.0 
Target Version1.2Fixed in Version1.2 
Summary0010614: Inconsitent naming of data in Responses
DescriptionThe 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.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Christian Grothoff

2025-11-14 23:49

manager   ~0026454

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.

Issue History

Date ModifiedUsernameFieldChange
2025-11-14 21:42htgoebelNew Issue
2025-11-14 23:49Christian GrothoffStatusnew => closed
2025-11-14 23:49Christian GrothoffResolutionopen => won't fix
2025-11-14 23:49Christian GrothoffProduct Version => 1.0
2025-11-14 23:49Christian GrothoffFixed in Version => 1.2
2025-11-14 23:49Christian GrothoffTarget Version => 1.2
2025-11-14 23:49Christian GrothoffNote Added: 0026454