Timeline for Golang Design Pattern for Generating View Objects in a REST API?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Aug 27, 2021 at 23:36 | review | First answers | |||
| Aug 28, 2021 at 2:26 | |||||
| S Aug 27, 2021 at 23:36 | history | edited | Omeri | CC BY-SA 4.0 | added 83 characters in body |
| Aug 27, 2021 at 22:58 | comment | added | Naftuli Kay | Yes, I've made the same choice to separate "views" (e.g. what the API returns) from the database models, as I certainly don't want to return a password hash accidentally. Unfortunately, this just means lots and lots of copying between structs and if a new database field is added, I have to find all the places it is referenced and add it, so it's easy to miss things. I'll look for Golang automappers. | |
| Aug 27, 2021 at 22:35 | comment | added | CommunityBot | Please provide additional details in your answer. As it's currently written, it's hard to understand your solution. | |
| S Aug 27, 2021 at 22:07 | review | First answers | |||
| Aug 27, 2021 at 22:35 | |||||
| S Aug 27, 2021 at 22:07 | history | answered | Omeri | CC BY-SA 4.0 |