Timeline for Must the use cases extend the entities in Clean Architecture?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 11, 2022 at 8:55 | vote | accept | Takesi Tokugawa YD | ||
| Sep 25, 2022 at 10:59 | comment | added | Filip Milovanović | This arrangement lets Use Cases make calls to things in the Interface Adapters layer without knowing what they actually are (without knowing their concrete types). This is achieved via dependency injection. Don't get confused by the fact that code in one layer also references/calls/implements things found in the next layer towards the center - that is always going to be the case. | |
| Sep 25, 2022 at 10:48 | comment | added | Filip Milovanović | "This answer let me know that I was wrong - the Use cases also including the interfaces of gateways (but not their implementations)." - you shouldn't think of them as the interfaces of Gateways/Controllers/Presenters; instead, you should see them as interfaces required by the Use Cases, that Gateways/Controllers/Presenters then implement. E.g. you wouldn't have a generic Presenter interface implemented by every Presenter, but Use Case–specific Presenter interfaces. As such, they help express application business rules (part of the use Use Code is written in terms of them). | |
| Sep 25, 2022 at 10:03 | answer | added | Ben Cottrell | timeline score: 3 | |
| Sep 25, 2022 at 8:57 | history | edited | Ben Cottrell | CC BY-SA 4.0 | Changed 'use case in an object' to 'use case is an object' as per the wording of the book. |
| Sep 25, 2022 at 7:36 | history | edited | Takesi Tokugawa YD | CC BY-SA 4.0 | added 37 characters in body |
| Sep 25, 2022 at 7:25 | history | asked | Takesi Tokugawa YD | CC BY-SA 4.0 |