I think many developers do that in Presentation layer, specifically in ViewModel/Presenter/Controller (not in Activity/Fragment/View!). My approach is to put that logic in Domain layer. Why? Is it presentation logic or domain logic? Presentation logic is something you decide “mapping render model”, “format of render model”, “how to render”, “what color, what size, which text”, … Read more
Export a symbol or a string along with your interface with the same name export interface IService { get(): Promise<string> } export const IService = Symbol(“IService”); Now you can basically use IService as both the interface and the dependency token import { IService } from ‘../interfaces/service’; @Injectable() export class ServiceImplementation implements IService { // Used … Read more
1. May the Presenter query information from the view To answer this to your satisfaction, we need more details about the particular case. Why can’t the view provide more context information directly upon callback? I suggest you pass the Presenter a Command object so the Presenter doesn’t have to know what to do in which … Read more
Clean architecture aims to separate the layers. Business Layer, Data Layer and Presentation Layer will be separate applications. Therefore you will increase the reusability for each one of them. MVVM as design pattern should be implemented in the Presentation Layer. Presentation Layer will interact with Business Layer (or Domain Layer) and the Business Layer will … Read more
I have been pondering the same thing and after finding very little on the subject, I have come to the conclusion “Yes” it is probably the best option. my reasoning as follows: Single Responsibility: If you can’t aggregate use-cases, then each can’t really be single responsibility. Without aggregation, it means domain logic ends up in … Read more
I put the transaction on the controllers. The controller knows about the larger framework since it probably has at least metadata like annotations of the framework. As to the unit of work, it’s a good idea. You can have each use case start a transaction. Internally the unit of work either starts the actual transaction … Read more
The term “Clean Architecture” is just the name of the article. The onion architecture is a specific application of the concepts explained in the article.