I understand how usecases should depend on entities, but I don't know how repositories depend on usecases. Say we want to store newly created users using userUsecase.register() to database, the usecase should know about the respective repository right? At least usecases know about the repository interface, not the implementation.
How do repositories depends on use cases in clean architecture
5.2k views Asked by BigLOL At
1
There are 1 answers
Related Questions in CLEAN-ARCHITECTURE
- php Variable name must change in for loop
- register_shutdown_function is not getting called
- Query returning zero rows despite entries existing
- Retrieving *number* pages by page id
- Automatically closing tags in form input?
- How to resize images with PHP PARSE SDK
- how to send email from localhost using codeigniter?
- Mariadb max Error while sending QUERY packet PID
- Multiusers login redirect different page in php
- Imaginary folder when I use "DirectoryIterator" in PHP?
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
Popular Tags
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Yes, the Use Case itself should only have a dependency to the repository interface and thus you should inject the repository interface into the use case. The repository interface should be defined in the application core layer (or domain layer).
The implementation of the repository interface will reside in the infrastructure layer (also referred to as persistence layer or data layer).
So that means the repository implementation does not depend on the use case. Both, the use case and repository implementation depend only on the repository interface instead. With this the Dependency Inversion principle is applied.
With that, all dependencies are pointing inwards which makes both the use cases and the repository implementation (infrastructure) dependent on the core layer. But the core (i.e. domain) layer does not have any dependencies to outer layers.