View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011095 | Taler | merchant backoffice SPA | public | 2026-02-17 15:34 | 2026-02-19 18:49 |
| Reporter | sebasjm | Assigned To | |||
| Priority | normal | Severity | tweak | Reproducibility | always |
| Status | confirmed | Resolution | open | ||
| Product Version | git (master) | ||||
| Target Version | 1.8 | ||||
| Summary | 0011095: better report base url | ||||
| Description | from comment: ``` Unlike what the API docs say the data source is not Base URL to request the data from, as it's not a base URL. It's a path relative to the merchant instance base URL ``` But I think we should have a list of "common reports" which the SPA is going to translate into the correct URL before sending the request to the backend. The user then select on from the list instead of writing the URL Additionally (and if needed) we can have a "other..." for a more custom report. Or a "custom" boolean flag which allows to apply small changes to a known URL. | ||||
| Tags | design-required, ux | ||||
|
|
Yes, indeed we shouldn't even allow the user (unless in developer mode) to specify the report target URL. For now, I propose we support the new statistics endpoint and /private/orders. Note that for both of these the SPA should have custom fields to allow passing query parameters. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-02-17 15:34 | sebasjm | New Issue | |
| 2026-02-19 18:49 | Christian Grothoff | Note Added: 0027816 | |
| 2026-02-19 18:49 | Christian Grothoff | Severity | minor => tweak |
| 2026-02-19 18:49 | Christian Grothoff | Status | new => confirmed |
| 2026-02-19 18:49 | Christian Grothoff | Product Version | => git (master) |
| 2026-02-19 18:49 | Christian Grothoff | Target Version | => 1.8 |
| 2026-02-19 18:49 | Christian Grothoff | Tag Attached: design-required | |
| 2026-02-19 18:49 | Christian Grothoff | Tag Attached: ux |
