"Use Case" Examples are leaking domain objects (entities) about clean-architecture-example HOT 1 CLOSED

Hi @eladchen

I might have to read that part again, to be honest I've never seen it as a problem. I might have misunderstood unclebob, but I see a use case as the owner of the business logic, so it makes sense for me to use domain objects.

I guess there is an edge case when a use case needs more information than an entity can hold, or needs to return a complex data structure. In that case it makes to create DTOs for input or output. But I would do it for convenience, rather than as a rule.

Does that make sense? This is just my interpretation by the way, it's possible that unclebob disagrees on this one.

Mattia

from clean-architecture-example.