Timeline for Is it okay for an Interface Adapter / Repository / Gateway to use Entities in its implementation
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 18, 2022 at 10:09 | comment | added | Bawenang Rukmoko Pardian Putra | I see. I'll take a not on that. BTW, so in that case, I can actually use Entities as a parameter or dependency for the Interface-Adapters / Gateway then? And in the View/ViewModels or the Presentation Layer itself then? I always map the entity to a DTO called Request Model for the Interface-Adapter (especially for API) and View Param for the Views. Because I was under the impression that we should really separate these layers. | |
| Sep 16, 2022 at 7:28 | comment | added | Rad80 | Entities are a component of the business logic. Configuration options are data structures too and you might use the same syntactic constructs to implement them, but the way you think about (and then treat) your "business" entities is different. As a general rule if the people that pay you to develop the software talk among themselves about the thing, it's part oif the domain. If it's stuff that is in the application because you need it, it is not. | |
| Sep 15, 2022 at 11:26 | comment | added | Bawenang Rukmoko Pardian Putra | Thanks. I was thinking that everything that is consistent on every app are Entities. So Entities should be the items that will reflect the business process in reality, is that it? I have a hard time separating these into their correct categorizations. I don't know what to look at to determine which on is which. | |
| Sep 9, 2022 at 11:01 | history | answered | Rad80 | CC BY-SA 4.0 |