View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007669 | Taler | documentation | public | 2023-02-09 16:07 | 2023-09-23 16:39 |
| Reporter | MS | Assigned To | Antoine A | ||
| Priority | normal | Severity | text | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Target Version | 0.9.4 | ||||
| Summary | 0007669: Document data types used in libeufin REST calls. | ||||
| Description | One example are amounts: there should be one document that specifies their format. Along this, the API docs have to point at those specifications whenever the said type is mentioned. The same way that Taler does with api-common.rst. | ||||
| Tags | No tags attached. | ||||
|
|
be6eb54..af11ed5 starts to address this. Notably, the size in bits of the integer part of amounts is not documented. |
|
|
Now done? |
|
|
Antoine: unless MS says this is done, maybe you can do a pass over the REST API (chapter 1.11) and see if there are any inputs/outputs that are still not properly documented. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-02-09 16:07 | MS | New Issue | |
| 2023-02-09 16:52 | MS | Note Added: 0019791 | |
| 2023-04-13 20:50 | Florian Dold | Project | libeufin => Taler |
| 2023-04-17 11:49 | Florian Dold | Target Version | => 0.9.4 |
| 2023-04-17 11:49 | Florian Dold | Summary | Document data types used in REST calls. => Document data types used in libeufin REST calls. |
| 2023-05-04 20:11 | Christian Grothoff | Severity | minor => text |
| 2023-09-23 15:46 | Christian Grothoff | Note Added: 0020527 | |
| 2023-09-23 16:38 | Christian Grothoff | Assigned To | => Antoine A |
| 2023-09-23 16:38 | Christian Grothoff | Status | new => assigned |
| 2023-09-23 16:39 | Christian Grothoff | Note Added: 0020532 |
