-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix: static을 제거하여 전역 접근 제거 #8
Conversation
GeonH0
commented
Jun 18, 2024
- Mapper는 특정뷰에 종속적으로 될거 같아 전역적으로 접근하는건 불필요 할거 같아 static을 제거 하여 전역 접근을 제거 하였습니다.
@@ -31,6 +31,7 @@ class RecipeListViewModel: InputRecipeListViewModel, OutputRecipeListViewModel { | |||
private let disposeBag = DisposeBag() | |||
private let fetchFeedListUseCase: FetchFeedListUseCase | |||
private let searchFeedListUseCase: SearchFeedListUseCase | |||
private let mapper = RecipeMapper() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
recipeListMapper로 더 명확한 네이밍을 가지면 좋을 것 같은데 어떻게 생각하시나요?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
d529f15 변경했습니다!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
좋아요! RecipeMapper 요 객체도 같이 변경되었으면 해요~
아무래도 레시피 서비스다 보니 Recipe로 시작하는 Mapper가 더 생길 것 같아서 명확히 하는게 좋을 것 같아요 😄
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
b5669b5
RecipeFetchMapper로 네이밍 변경했습니다!
302230b
to
cdc8dfa
Compare
Mapper는 Presentation Layer에 속하기 때문에 Fetch 같은 로직을 담는 네이밍 보다는 UI에 가까운 네이밍을 선택하는 게 어때요? |
Quality Gate passedIssues Measures |