Conversation
- Add UseCase interface in user/usecase package defining core operations - Update UserUseCase constructor to return UseCase interface instead of concrete type - Refactor DI container to use UseCase interface throughout - Update HTTP server and handler to depend on UseCase interface - Remove duplicate UserUseCaseInterface from HTTP handler - Remove internal field assertion in usecase test This change improves testability and decouples HTTP layer from concrete usecase implementation, following dependency inversion principle.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This change improves testability and decouples HTTP layer from concrete usecase implementation, following dependency inversion principle.