View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008258 | Taler | wallet-core | public | 2024-01-24 15:29 | 2024-07-25 23:56 |
| Reporter | Florian Dold | Assigned To | Florian Dold | ||
| Priority | low | Severity | tweak | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Target Version | post-1.0 | ||||
| Summary | 0008258: consider providing fluent interface for amount/date types, review date and amount type hierarchy [12h] | ||||
| Description | We currently provide many different data types (absolute, relative, precise, protocol-rounded, DB stamps). We should do computations with only a single type (or rather class) for absolute and relative timestamps, and then properly convert to the other types. We should avoid doing direct computation with the other types. Similar considerations apply to amount types (AmountString vs AmountJson). Instead of AmountJson, there should be one opaque immutable amount type and the AmountString we use in interfaces. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-01-24 15:29 | Florian Dold | New Issue | |
| 2024-01-24 15:29 | Florian Dold | Status | new => assigned |
| 2024-01-24 15:29 | Florian Dold | Assigned To | => Florian Dold |
| 2024-04-03 13:18 | Florian Dold | Summary | consider providing fluent interface for amount/date types, review date and amount type hierarchy => consider providing fluent interface for amount/date types, review date and amount type hierarchy [12h] |
| 2024-04-05 14:57 | Christian Grothoff | Target Version | 0.11 => 0.14 |
| 2024-07-25 23:56 | Christian Grothoff | Target Version | 0.14 => post-1.0 |
