In Clean Architecture, it's not typical to send use cases to the repository constructor. The repository's responsibility is to provide an abstraction over data access, not to interact directly with business logic or use cases.
I really like the way you teach clean architecture. I would say it is the best content I have seen so far please continue making great videos! One thing you can improve is that when you are writing code add some empty lines and the end of the file so the code would not be in the bottom of screen and covered by subtitles!
In Clean Architecture, it's not typical to send use cases to the repository constructor. The repository's responsibility is to provide an abstraction over data access, not to interact directly with business logic or use cases.
I really like the way you teach clean architecture.
I would say it is the best content I have seen so far please continue making great videos!
One thing you can improve is that when you are writing code add some empty lines and the end of the file so the code would not be in the bottom of screen and covered by subtitles!
Good explanation. Yes this how we do it ... very clean 🙂
Great !!, for Daya Layer I use Dto and Entity and for UI I use Model
Viewmodel gets usecase in the constructor param and usecase gets repository in the constructor param.
Why would a repository invoke a usecase?