You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed the sample is not following the dependency rule proposed by the linked article Clean Architecture.I.e. GetTasks uses the Task Repository, which belongs to the data package. I would argue it is a style common when writing a 3-layer architecture where the TaskRepository is used as a Port to access the data layer.
In clean architecture the depencendy rule would force us to have a interface inside the domain layer which is implemented by some class in the data layer. As it is very common to have some kind of persistence, we could say we break the rule for convinience? How do we apply the dependency rule to other cases where domain logic wants to talk to the outside world i.e. Messaging or Sharing information.
What do you think? How did you manage this in practice ?
The text was updated successfully, but these errors were encountered:
I noticed the sample is not following the dependency rule proposed by the linked article Clean Architecture.I.e. GetTasks uses the Task Repository, which belongs to the data package. I would argue it is a style common when writing a 3-layer architecture where the TaskRepository is used as a Port to access the data layer.
In clean architecture the depencendy rule would force us to have a interface inside the domain layer which is implemented by some class in the data layer. As it is very common to have some kind of persistence, we could say we break the rule for convinience? How do we apply the dependency rule to other cases where domain logic wants to talk to the outside world i.e. Messaging or Sharing information.
What do you think? How did you manage this in practice ?
The text was updated successfully, but these errors were encountered: