Timeline for Clean Architecture Chapter 8 - Financial Data Mapper
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4, 2024 at 22:24 | history | edited | candied_orange | CC BY-SA 4.0 |
added 4 characters in body
|
| Dec 4, 2024 at 22:23 | comment | added | candied_orange | @Tozine OCP and DIP are considerations but what this diagram tells you more than anything else is what knows about what. That's the big lesson any UML class diagram teaches. | |
| Dec 4, 2024 at 22:17 | comment | added | Tozine | Looking at your response and those of others, I conclude that the implementation itself doesn't matter much, for two reasons. First, the diagram doesn't focus on implementation per se, but on the OCP. Second, how models are implemented outside the boundaries doesn't really matter, as the core is protected by interfaces and dependency inversion. Uncle Bob has an approach different from what I'm used to, likely due to years of experience and different contexts. Perhaps this is why I’ve become so attached to simple details like the "naming" of boxes. Thank you. | |
| Dec 4, 2024 at 21:27 | history | edited | candied_orange | CC BY-SA 4.0 |
added 120 characters in body
|
| Dec 4, 2024 at 21:14 | history | answered | candied_orange | CC BY-SA 4.0 |