Timeline for Creating Controllers and Repositories without corresponding Models
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 30, 2023 at 13:48 | history | edited | Christophe |
edited tags
|
|
| Jul 30, 2023 at 13:45 | vote | accept | Akari Oozora | ||
| Jul 30, 2023 at 9:52 | answer | added | Christophe | timeline score: 1 | |
| Jul 30, 2023 at 7:05 | review | Close votes | |||
| Aug 14, 2023 at 3:07 | |||||
| Jul 30, 2023 at 6:51 | comment | added | Ben Cottrell | Build whatever makes most sense for your UI/UX and user journeys in your app. I'd recommend avoiding the trap of letting the database structure influence the code. I would typically not expect database entities to have any kind of neat mapping on to classes in your program (avoiding using table names to decide how to structure your code), as Database structure is about persistence and integrity of the data. On the other hand, your code structure exists to provide behaviour, so look at class names that make sense from a user behaviour or UX point of view | |
| S Jul 30, 2023 at 4:33 | review | First questions | |||
| Jul 30, 2023 at 13:47 | |||||
| S Jul 30, 2023 at 4:33 | history | asked | Akari Oozora | CC BY-SA 4.0 |