Timeline for How to handle validation errors from API response when using repository pattern
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2021 at 18:24 | answer | added | Scott Hannen | timeline score: 0 | |
| Apr 25, 2021 at 20:29 | vote | accept | user2190492 | ||
| Apr 25, 2021 at 20:25 | answer | added | Ewan | timeline score: 3 | |
| Apr 25, 2021 at 15:01 | history | edited | user2190492 | CC BY-SA 4.0 | edited body |
| Apr 25, 2021 at 14:48 | comment | added | user2190492 | Well, unless the serverside validation also uses some logic that can only be checked on the server. Like checking if a username already exists. Or maybe even that a concurrent request of another client instance changed data/state on the server between clientside and serverside validation. | |
| Apr 25, 2021 at 12:17 | comment | added | Rik D | ‘Although the [...] errors I mention are rare, and would theoretically never occur on the serverside validation.’ So they only occur in exceptional situations? | |
| Apr 25, 2021 at 10:45 | history | asked | user2190492 | CC BY-SA 4.0 |