View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0010539 | Taler | merchant backoffice SPA | public | 2025-10-29 18:26 | 2025-10-29 18:26 |
| Reporter | sebasjm | Assigned To | sebasjm | ||
| Priority | normal | Severity | feature | Reproducibility | have not tried |
| Status | assigned | Resolution | open | ||
| Product Version | 1.2 | ||||
| Summary | 0010539: complete error handling on button actions | ||||
| Description | currently there is not clear way on how an error operation shows an error on a ui and this leads to wrong error messages, undetectable uncatched exceptions and missing i18n translations of error messages. We need an unified (all webapps) way of handling error catching and reporting. So I have defined a "safe" button handler which: * takes a function that returns an operation result (the operation already defined happy path and error path with error codes) * requires an onFail and onSuccess handlers which may returns an explanation in case of any of this path * these handlers never throws, and unhandled cases shows generics errors (unhandled cases should be extremely rare if the software specification is complete) Also, building and using these handlers make the webapp testable. We now can define, run and verify the behavior of ui components with this "safe" handler interface (given an input, trigger an action and check the next state) which before was not standardized. kyc, challenger, aml, bank are already complete (which has a moderm ui), marchant backoffice is a challenge because the code is older and worse. webex will be out of scope for now. This is already being worked on dev/sebasjm/error-handling, rebased periodically. | ||||
| Tags | No tags attached. | ||||
